If you look at the code for the ssl demo programs, you'll see that it calls
'ERR_print_errors_fp(stderr)' to check the errors for 'SSL_connect()'. If
you look at the code for that function, you should be able to add code to
your interface to report more of an error back.
I know that when I tried to compile the cli/serv demo program in ssl on
WinNT, I was getting 'SSL_connect()' returning a "-1" because it was
reporting a "PRNG not seeded" error. This I fixed by reading back through
the archive and also by looking at <openssl/rand.h>. There are a few
Windows functions in there that "seed the PRNG" like RAND_screen().
I hope this helps.
Jay Repko
Computer Engineer
NUWC
-----Original Message-----
From: Angelo Nardone [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 16, 2000 4:36 PM
To: [EMAIL PROTECTED]
Subject: Windows COM SSL_connect problems
I tried to make a ssl connection inside of a COM (dll).
The COM try to 'post' some data to a secureweb server (https).
This work fine in Linux an FreeBSD, but when I tried to use in a Windows
routine, the 'SSL_connect' return "-1".
Some body know the why?
I include the source code of the 'interfase'.
SSLeay_add_ssl_algorithms();
SSL_METHOD *meth = SSLv2_client_method();
SSL_load_error_strings();
SSL_CTX *ctx = SSL_CTX_new (meth);
if (ctx == NULL)
return 0;
<snip>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
