Just seeking advice/things to consider for deadlock (or 'wait') on a 
SSL_Connect(). Unfortunately it stalls here, so there's no return code.

The project establishes a number of SSL conns between various application 
instances. It's in C++, where standard socket libs are used to establish the 
connection, SSL added via SSL_Set_Fd and then SSL_connect()/accept(). Normal 
sockets (i.e. without SSL) are used for local inter-proc comms - maybe this is 
relevant?

I've been stuck for a while - and advice as to common 
areas/mistakes/considerations are most appreciated.

Thanks!
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to