When dealing with the high level SSL_* functions, stick with SSL_get_error() as per s_client.c and s_server.c.
If you are doing things on a lower level, you may need to deal with the error stack yourself; but for people new to OpenSSL, just stick with functions starting with SSL_* or BIO_* On Fri, Feb 12, 2010 at 10:59 PM, Patrick M. Rutkowski <rutsk...@gmail.com> wrote: > I should have mentioned ERR_get_error() in my question, that's what's > most heavily on my mind. The question is if you have to call clear the > error stack with ERR_get_error() after every failed SSL call, even > failures that are often "not really failures." For example, my code > considered SSL_read() returning > SSL_ERROR_WANT_READ/SSL_ERROR_WANT_WRITE to be a sort of "success", > and so I accidentally forgot to clear the error stack. I wish the man > pages had reminded me to. > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-us...@openssl.org > Automated List Manager majord...@openssl.org > -- John L Veazey Platypus & Wombat Lead Developer Toll Free: 1-888-752-8978 Web: http://platypus.tucows.com ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
