On Thu, December 6, 2012 09:05, Ludo Brands wrote: > On 02/12/2012 23:53, Tomas Hajny wrote: >> Hello everybody, >> >> I guess that it may be easier if I post some additional information >> here myself... >> >> As outlined by Waldo previously, the simple test accessing a HTTPS >> URL fails under OS/2 (while accessing HTTP URL works flawlessly). The >> bad thing about it is that it doesn't give much clue what is wrong. >> Tracing through it line by line in gdb, I get -1 result from the >> function _SSLConnect (as imported from the OpenSSL DLL) and >> immediately afterwards (in ssl_openssl.SSLCheck) I get result 0 (i.e. >> no error) from _ErrGetError. :-( Similarly, the WinSock function >> WSAGetLastError shows no error (remember, I use the OS/2 WinSock >> emulation layer for porting Synapse to OS/2). I can also see (from >> the OS/2 socket API tracing utility) that the socket has been opened >> properly before that; it's "just" that the OpenSSL library doesn't >> like it somehow (just in case - attached is the trace output for >> testing HTTP and testing HTTPS)... :-( . . > 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? > have another app using openssl. It would be worthwhile to take a winsock > trace and see if the openssl handshake shows up. I cannot provide Winsock trace for the other application (it doesn't use the Winsock layer which was included in OS/2 just as an additional emulation layer for easier porting from MS Windows and the used tracing facility is really specific for the winsock library), but I can provide the corresponding IP dump if that helps (that obviously wouldn't show the API parameters and return values, etc., but only the generated IP traffic). > _SSLConnect returning -1 and _ErrGetError returning 0 sounds like > SSL_library_init() wasn't called or failed somewhere but then other > openssl functions would probably have failed before. It does suggest a SSL_library_init() is called. > fatal error in openssl. You can try forcing SSLType to one of the > TSSLType values (default=LT_all) to see if you get a more meaningful > error message. Check also that SslMethodV23, SslMethodTLSV1, etc are not > nil. OK, I will try that and let you know the results. 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
