On 1/3/2011 4:22 AM, Uri Simchoni wrote:
I’m using OpenSSL 0.9.8i, and have noticed the following scenario:
-Some OpenSSL crypto function returns with an error, leaving a
description of the error on the error queue
-The application neglects to call ERR_clear_error()
-SSL_read() is then called on a non-blocking socket and returns because
there’s no input available
-Calling SSL_get_error() returns SSL_ERROR_SSL instead of
SSL_ERROR_WANT_READ, because the error queue is not empty.
Unfortunately, this is documented behavior.
http://www.openssl.org/docs/ssl/SSL_get_error.html
IMO, it's broken. But it is documented, so you have to make it work somehow.
DS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
