[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openssl-dev
Subject:    Re: [openssl.org #514] Bug in OpenSSL????
From:       Arne Ansper <arne () ats ! cyber ! ee>
Date:       2003-02-22 11:59:16
[Download RAW message or body]



> >>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                       openssl-dev@openssl.org
Automated List Manager                           majordomo@openssl.org
[prev in list] [next in list] [prev in thread] [next in thread]