Thank you for your help. It turned out that the library we were using that implemented the OpenSSL calls was not properly handing the SSL_ERROR_SYSCALL when errno was EAGAIN. After discovering that ERR_get_err returned 0, I began to suspect that something I read about EAGAIN being equivalent to EWOULDBLOCK (under HP-UX) was true. It sets EAGAIN to let you know the call would block and to try again. Which is what we did and it worked great.
Thanks for your help. Kevin -----Original Message----- From: Lutz Jaenicke [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 8:57 AM To: [EMAIL PROTECTED] Subject: Re: FW: SSL_ERROR_SYSCALL On Mon, Nov 18, 2002 at 08:00:16AM -0800, Moffet, Scott wrote: > err is being set to -1 > SSL_get_error is returning SSL_ERROR_SYSCALL > errno is 11, EAGAIN > ERR_get_error is returning 0 In fact, SSL_ERROR_SYSCALL is the "catchall" message that is given when no other condition applies. > err is -1, what is 5, errno = 11, err_err = 0 > > Is this a problem with non-blocking sockets? Hmm. No. > (And if this helps at all, the output of openssl s_server is: > . > . > SSL_accept: SSLv2 write server hello A > SSL_accept: failed in SSLv2 read client masterkey A > > then the connection closes) Does ssldump give you any indication? In any case, what is the platform? I vaguely remember having discussed problems with non-blocking behaviour on Windows... Best regards, Lutz -- Lutz Jaenicke [EMAIL PROTECTED] http://www.aet.TU-Cottbus.DE/personen/jaenicke/ BTU Cottbus, Allgemeine Elektrotechnik Universitaetsplatz 3-4, D-03044 Cottbus ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
