>Probably it's a non-blocking socket? Either switch to blocking I/O if
>that is appropriate, or browse the openssl-dev mailing list archives
>for information on how to use non-blocking I/O correctly.
It was non-blocking, but after setting it back to blocking I still get
the same thing: -1 from SSL_connect(), and no error message from
ERR_print_errors_fp().
I can send the full sources if you want to play with it.
By the way, if some of you have gotten no-Bcc spam warnings from
acme.com, I apologize. I did add an exception to my spam filter
for *@openssl.org before I added myself to the mailing list, but
for some reason that didn't work. If it keeps up I'll take myself
off the list.
---
Jef
Jef Poskanzer [EMAIL PROTECTED] http://www.acme.com/jef/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
