Hi, Can you tell me, is this a bug in all versions, even OpenSSL 0.9.8i?
Solveig On Sat, Oct 4, 2008 at 6:45 PM, David Schwartz <[EMAIL PROTECTED]> wrote: > > > Thank you for your response. I have checked the > > error code using SSL_get_error. > > > I get an SSL_ERROR_SYSCALL (5) return code, > > indicating an I/O, but the error queue is empty. > > My application continues to function. It is fetching > > an HTML document over an HTTPS connection. > > This is a documented bug in OpenSSL, however I don't know what the bugfix > or > workaround is. Here's the documentation for when SSL_shutdown returns 0: > > "The shutdown is not yet finished. Call SSL_shutdown() for a second time, > if > a bidirectional shutdown shall be performed. The output of > SSL_get_error(3) > may be misleading, as an erroneous SSL_ERROR_SYSCALL may be flagged even > though no error occurred." > > The problem is, how do you know when to call SSL_shutdown again? If it's > immediate, will the problem simply repeat giving you an SSL_ERROR_SYSCALL > again? > > I think one possible imperfect workaround is to call SSL_shutdown again if > you get SSL_ERROR_SYSCALL. If you get SSL_ERROR_SYSCALL again, treat it as > a > successful shutdown. > > DS > > > > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager [EMAIL PROTECTED] > -- Solveig Viste Instantiations VA Smalltalk Support
