On Thu, December 6, 2012 10: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? . .
It should be transparent, but I'll re-check it at least at the OS level (netstat shows the socket number and it should hopefully match the number provided in Winsock trace). Do you have an idea for a test which I could adapt to open a socket using Winsock and use/access it via standard BSD sockets afterwards (obviously, that test would need to use the respective sockets API rather than Synapse)? Tomas ------------------------------------------------------------------------------ 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
