> From: owner-openssl-us...@openssl.org On Behalf Of Alexander Lamaison
> Sent: Friday, 07 August, 2009 08:15
> 2009/8/7 Dave Thompson :
>
> I our case (the libssh2 library) we don't have an EXE to
> compile OpenSSL_Applink into (you cant just compile it into a
> DLL because it doesn't get ca
2009/8/7 Dave Thompson :
>> From: owner-openssl-us...@openssl.org On Behalf Of Alexander Lamaison
>> Sent: Thursday, 06 August, 2009 09:12
>
>> I'm trying to avoid passing any C-runtime objects (such as a
>> FILE*) across the OpenSSL DLL boundary. This is unsafe as
>> the two DLLs may be using dif
> From: owner-openssl-us...@openssl.org On Behalf Of Alexander Lamaison
> Sent: Thursday, 06 August, 2009 09:12
> I'm trying to avoid passing any C-runtime objects (such as a
> FILE*) across the OpenSSL DLL boundary. This is unsafe as
> the two DLLs may be using different runtime instances whic
I'm trying to avoid passing any C-runtime objects (such as a FILE*)
across the OpenSSL DLL boundary. This is unsafe as the two DLLs may
be using different runtime instances which causes crashes on Windows.
Apparently using BIO_new_file is a safe way to pass a file to a
function as the FILE* is cre
