W3C home > Mailing lists > Public > www-lib@w3.org > April to June 2000

SSL connect fails

From: Sander Alberink <Sander.Alberink@cmg.nl>
Date: Tue, 23 May 2000 14:32:19 +0200
Message-ID: <11A760648FE3D211BE5200A0C9F2A1945A83FF@NL-ENS-MAIL01>
To: www-lib@w3c.org
Cc: openssl-dev@openssl.org

We are using libwww-ssl to fetch pages from secure webservers on the
internet, but we find that there are some problems in the way this happens.
Since requests failed in strange ways, we conducted tests to see where the
connection attempts failed. After increasing the logging using in libwww, it
became obvious that it was the SSL connect stage that failed every time.
Further investigation revealed that this problem appears only when the
connect was done using a non-blocking socket.
Searching the mailing-lists, it seemed that we are not the only ones having
problems using OpenSSL/libwwwssl with non-blocking sockets. Did anybody
verify whether or not there is a bug in OpenSSL regarding SSL_connect on a
nonblocking socket?

At this moment, we have patched libwwwssl so that just before the connect
the socket is put into blocking mode and after the connect has succeeded it
is put back in non-blocking mode. Somehow I feel that this is a kludge and
that the real problem is in OpenSSL.

Anybody care to comment?

The woods are lovely, dark and deep,
But I have lines to code before I sleep, lines
to code before I sleep.

Received on Tuesday, 23 May 2000 08:31:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:52 UTC