From: owner-openssl-us...@openssl.org On Behalf Of Dan Maartens
Sent: Monday, 13 April, 2009 20:31
Thanks for your response Dave. With -state and -msg enabled,
[s_server] seems to be hanging after SSL_accept:SSLv3 flush data.
When I abort the client at this point
Thanks for your response Dave. With -state and -msg enabled, it seems to be
hanging after SSL_accept:SSLv3 flush data. When I abort the client at this
point (as it will retry forever with no success), I get: failed in SSLv3
read client certificate A.
Given the stupefying nature of this problem,
I'm attempting to establish an SSL connection, where everything
seems OK until SSL_connect, which returns -1. error is set to 11,
and perror() gives Resource temporarily unavailable.
ERR_error_string rather useless output:
error:0002:lib(0):func(0):system lib, even though both
Hi David,
This is on SuSE 10.3. The socket is non-blocking, for the only reason that I
thought it would make debugging the problem easier. With the socket in
blocking mode (which is all I need), I have the problem where SSL_connect
never returns.
I'm looking at errno becuase the information
From: owner-openssl-us...@openssl.org On Behalf Of Dan Maartens
Sent: Friday, 10 April, 2009 18:39
This is on SuSE 10.3. The socket is non-blocking, for the only
reason
that I thought it would make debugging the problem easier.
With the socket in blocking mode (which is all I need),
This is on SuSE 10.3. The socket is non-blocking, for the only reason
that I thought it would make debugging the problem easier.
Debugging non-blocking sockets is much more complex than blocking ones.
With the socket in blocking mode (which is all I need), I have the
problem where
Hello,
I'm attempting to establish an SSL connection, where everything seems OK
until SSL_connect, which returns -1. error is set to 11, and perror() gives
Resource temporarily unavailable. ERR_error_string rather useless output:
error:0002:lib(0):func(0):system lib, even though both
Very probably an error due to using non-blocking sockets: EWOULDBLOCK.
It's a retriable error.
For pure sockets I/O, no SSL, see W. Richard Stevens's books and other
resources on using nonblocking sockets with connect, read, write,
send, recv, etc.
On UNIX and Windows for pure sockets, most of
