>>> If I have correctly understood the FAQ about the OPENSSL_applink. It
>>> applies only in the Win32 version:
>>>
>>> * If OPENSSL_USE_APPLINK is not defined at the compilation stage of
>>> OpenSSL, the snippet applink.c is not mandatory BUT I have to
>>> build a debug and a relea
> I actually ended up solving it by removing all uses of BIO_new_fp() in
> favor of my own custom BIO that I just finished writing earlier this
> week.
Why not BIO_new_file?
>>> Yeah, I discovered while analyzing the code that using BIO_new_file()
>>> rather than BIO_new_fp() woul
Andy Polyakov schrieb:
I actually ended up solving it by removing all uses of BIO_new_fp() in
favor of my own custom BIO that I just finished writing earlier this
week.
>>> Why not BIO_new_file?
>>
>> Yeah, I discovered while analyzing the code that using BIO_new_file()
>> rather th
Hello Andy,
Thank you very much for answering
Andy Polyakov a écrit :
If I have correctly understood the FAQ about the OPENSSL_applink. It
applies only in the Win32 version:
* If OPENSSL_USE_APPLINK is not defined at the compilation stage of
OpenSSL, the snippet applink.c is not man
> There was suggestion to fall back to wfopen from a vmware engineer a while
> ago, but he couldn't provide patch (not that it would be very complex) and
> it was not followed up. Idea must have been something similar to just
> committed http://cvs.openssl.org/chngview?cn=19610.
Sounds like a good
I actually ended up solving it by removing all uses of BIO_new_fp() in
favor of my own custom BIO that I just finished writing earlier this
week.
Why not BIO_new_file?
Yeah, I discovered while analyzing the code that using BIO_new_file()
rather than BIO_new_fp() would disengage applink, howeve
On Tue, Apr 20, 2010 at 2:33 PM, Andy Polyakov wrote:
>>
>> I actually ended up solving it by removing all uses of BIO_new_fp() in
>> favor of my own custom BIO that I just finished writing earlier this
>> week.
>
> Why not BIO_new_file? A.
Yeah, I discovered while analyzing the code that using
Just two days ago I was banging my head against this very problem. I
have a C# app that calls into a C++ DLL that utilizes OpenSSL. Adding
applink.c to the DLL project didn't get rid of the error like I hoped it
would, and after analyzing the OpenSSL code I discovered to my dismay
that it alw
If I have correctly understood the FAQ about the OPENSSL_applink. It
applies only in the Win32 version:
* If OPENSSL_USE_APPLINK is not defined at the compilation stage of
OpenSSL, the snippet applink.c is not mandatory BUT I have to
build a debug and a release version of OpenSSL
2010/4/16 Patrice Guérin
> This way, OPENSSL_Applink can be used inside DLLs, but I'm not sure of
> implications so I need your advices.
>
I'm not an OpenSSL developer, but I think being able to set the Applink
function pointer explicitly is an excellent idea!
Just two days ago I was banging m
Hello All,
First of all, I'm new in OpenSSL and I need your advices . Please,
excuse my poor english.
If I have correctly understood the FAQ about the OPENSSL_applink. It
applies only in the Win32 version:
* If OPENSSL_USE_APPLINK is not defined at the compilation stage of
OpenSSL,
11 matches
Mail list logo
