My point was... why on Linux did I need only libssl and to compile the same
client on Windows/MinGW requires libssl and libeay32. I could not find a
lot of doc about the differences between the two. The only thing I've found
said libeay32 is the predecessor of openssl. Is that right ?
Dr
On Wed, Mar 01, 2006, Chandi Bernier wrote:
My point was... why on Linux did I need only libssl and to compile the same
client on Windows/MinGW requires libssl and libeay32. I could not find a
lot of doc about the differences between the two. The only thing I've found
said libeay32 is
Chandi Bernier wrote:
My point was... why on Linux did I need only libssl and to compile the
same client on Windows/MinGW requires libssl and libeay32.
Something's wrong.
You either want libssl + libcrypto, or libssl32 + libeay32.
On Linux the reason it -probably- worked is that
1.
William A. Rowe, Jr. wrote:
Chandi Bernier wrote:
My point was... why on Linux did I need only libssl and to compile the
same client on Windows/MinGW requires libssl and libeay32.
Something's wrong.
You either want libssl + libcrypto, or libssl32 + libeay32.
Whoops - you either want
Hey guys,
I've tried a precompiled windows version of 0.9.7.c openssl and it was
lacking symbols for these 3 fnc :
ERR_print_errors_fp
BIO_new_socket
OPENSSL_add_all_algorithms_noconf (or conf)
Then I've decided on compiling my own version using mingw... which worked.
But it's still lacking
This brings up a really interesting point.
What is the appropriate separation of functions? What can I presume
is in each library? (eay32 is crypto stuff. ssl32 should be the BIO
and SSL session management stuff?)
-Kyle H
On 2/28/06, Chandi Bernier [EMAIL PROTECTED] wrote:
Hey guys,
I've
On Tue, Feb 28, 2006, Kyle Hamilton wrote:
This brings up a really interesting point.
What is the appropriate separation of functions? What can I presume
is in each library? (eay32 is crypto stuff. ssl32 should be the BIO
and SSL session management stuff?)
libssl or its equivalent is
