> >>Methods SSL_connect(), SSL_read() and SSL_write() should return > >>SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE if they need to complete > >>their tasks but the socket couldn't handle all the work. > >> > >>But instead, the methods return SSL_ERROR_SYSCALL when the underlying > >>socket gave errno=EWOULDBLOCK or errno=EAGAIN (means: the application > >>should retry with these functions if it has not been completed, yet) > >>from their respective functions (read() and write()).
I had a same error under Linux. The problem was that I had some junk left in error stack and faulty logic inside SSL_get_error caused the SSL_ERROR_SYSCALL to be returned. Try to do ERR_clear_error before SSL_read, SSL_write and SSL_connect see if it helps. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
