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)... :-( > > Obviously, any advices are most welcome, but my main questions are: > > 1) Are there any other ways how to obtain some additional information > regarding what goes wrong within the OpenSSL library (note that I use > this library with other applications - although not written by me or > in Pascal - i.e. it shouldn't be just a buggy OpenSSL DLL binary). > > 2) I noticed that file winsock2.txt included in the released version > stresses that Winsock version 2 is necessary, however sswin32.inc > provides support for Winsock 1.1 if compiled with WINSOCK1 > conditional symbol defined. Are there reasons why Winsock 1.1 should > not be sufficient for the SSL support (or more generally, what are > the potential issues with Winsock 1.1 unless talking about newer > functionality like IPv6 support)? > > I'm obviously looking forward to provide my Synapse modifications > necessary for OS/2 support to anyone interested for inclusion in the > distribution, but I guess that the discovered problems should be > fixed first. Anybody having opportunity to play with it directly > under OS/2 may get the patches immediately, of course. > > Thanks in advance > > Tomas > Tomas,
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 have another app using openssl. It would be worthwhile to take a winsock trace and see if the openssl handshake shows up. _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 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. 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
