On 06/12/2012 16:16, waldo kitty wrote: > On 12/6/2012 04:48, Ludo Brands wrote: >>>> I don't have os/2 and can't do any testing myself. Looking at the >>>> winsock traces there is nothing obvious that jumps out although I would >>>> have expected some handshaking coming from openssl. You indicated you >>> If I understand it correctly, this handshake is normally initiated by >>> SSLConnect (which fails here i.e. the handshake does not happen), right? >>> >> Yes, unless openssl on OS/2 doesn't use winsock which your next >> paragraph suggests but then we have potentially another problem: >> TSSLOpenSSL.Connect passes a socket handle to openssl obtained with >> winsock. Is the winsock handle a transparent socket handle and usable by >> non-winsock apps? > so if i'm understanding this, you are saying that the openssl dlls on OS/2 may > not be able to use the winsock but are possibly instead compiled for "raw" > (proper term?) access on the network stack? > > The winsock trace doesn't show any ssl handshake. So, or the openssl library is broken, badly initialized or whatever, or openssl talks to the server using the native berkeley sockets instead of winsock.
Ludo ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
