On Sun, 01 Oct 2006 17:15:44 +0300, Eugene Paskevich <[EMAIL PROTECTED]> wrote:
I'll perform some more tests this night and will report here.
At last I can report on this, sorry for such delay. Environment: Two users (me and my bro) located far away from each other. Both sides are behind NAT with port-forwarding and clients were compiled with OpenSSL support. Direct messaging works flawlessly in both ways. When I refer to v.1.3.2, I speak about the one from the site's main page. V.1.3.4 is the latest svn revision. I have made the following tests: 1) Me -> Bro; 1.3.4 -> 1.3.2; Remote client does not support OpenSSL. 2) Bro -> Me; 1.3.2 -> 1.3.4; Success. 3) Me -> Bro; 1.3.4 -> 1.3.4; Success. 4) Bro -> Me; 1.3.4 -> 1.3.4; Success. 5) Me -> Bro; 1.3.2 -> 1.3.2; Remote client does not support OpenSSL. 6) Bro -> Me; 1.3.2 -> 1.3.2; Remote client does not support OpenSSL. 7) Me -> Bro; 1.3.2 -> 1.3.4; Success. 8) Bro -> Me; 1.3.4 -> 1.3.2; Remote client does not support OpenSSL. In all unsuccessful steps the one, who is being requested to open SSL channel, sees the following in the Network Log: (not the one, who requests) [TCP] Secure channel request from _nickname_ (_UIN_). [SSL] SSL_accept error = 1408f10b, s3_pkt.c:299 [TCP] Closing connection to _UIN_. The one, who requests sees the following: [TCP] Sending request for secure channel to _nickname_ (#6). [TCP] Secure channel response from _nickname_ (_UIN_). [TCP] _nickname_ (_UIN_) does not support OpenSSL. Since there is no file, named s3_pkt.c in licq source, I can conclude that it is one of openssl files, but I did not check this out. I've tried to google a bit and see that such error is quite common. But still, there was some change in ssl in 1.3.4... ;-) -- Eugene Paskevich | *==)----------- | Plug me into [EMAIL PROTECTED] | -----------(==* | The Matrix
