Hi Stephan,
I didn't handle properly fd_write and fd_read events after ssl_accept
returning WANT_READ or WANT_WRITE. So sometimes SSL handshake didn't
complete succesfully. I use plain socket descriptors with some WSA functions
for selecting events, instead of MFC-Windows AsyncSocket classes.
Solved!
--
View this message in context:
http://openssl.6102.n7.nabble.com/ssl-connect-fails-Windows-Non-blocking-tp45348p45480.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
__
OpenSSL Project
Hi Titonus,
would you care to share the solution? I am interested too.
Cheers,
Stephan
On Tue, Jun 11, 2013 at 12:07 PM, titonus tito...@gmail.com wrote:
Solved!
--
View this message in context:
http://openssl.6102.n7.nabble.com/ssl-connect-fails-Windows-Non-blocking-tp45348p45480.html
More info:
Client SSL log:
[SSL_connect:before/connect initialization]
[SSL_connect:SSLv2/v3 write client hello A]
[SSL_connect:Error en SSLv2/v3 read server hello A]
[SSL_connect:SSLv3 read server hello A]
[SSL_connect:SSLv3 read server certificate A]
[SSL_connect:SSLv3 read server key exchange
OpenSSL latest version I use.
This is the bad sequence, client and server are already connected at TCP
level:
Client -- ssl_connect returns WANT_READ, so I've wait for next
select/WSAEventSelect
--- SSLv2/v3 read server hello A
Server -- ssl_accept returns WANT_READ, same wait
--- SSLv3 read
