On Wed, 30 Nov 2005 08:23:29 +0900 Jon Keating (JK) wrote: JK> On 11/27/05, Udo A. Steinberg <[EMAIL PROTECTED]> wrote: JK> > 16:17:45: [TCP] Secure channel response from XXX (317319???). JK> > 16:17:45: [TCP] XXX (317319???) does not support OpenSSL. JK> JK> I get an error that says: [SSL] SSL_accept error 0, SSL_5 JK> JK> I looked it up in ssl.h and it means syscall error. Which is rather JK> cryptic. I'm using OpenSSL 0.9.7e. I'll try to upgrade later and see JK> if it is fixed. JK> JK> What versions of OpenSSL are you guys using? The error shown above JK> will only be shown on the side that sends the request.
As I already said, I'm using OpenSSL 0.9.7g. Contrary to your statement
I'm seeing SSL errors on the side that is receiving the secure channel
request.
Here's a log of someone trying to open a secure channel to me:
14:31:41: [TCP] Reverse connecting to 317319XXX at 141.XX.YY.ZZ:32780.
14:31:41: [WRN] Reverse connect to 317319XXX failed:
Transport endpoint is not connected.
14:31:41: [TCP] Connection from XXX (317319XXX) [v8].
14:31:42: [TCP] Secure channel request from XXX (317319XXX).
14:31:44: [SSL] SSL_accept error = 1408f10b, s3_pkt.c:297
14:31:44: [TCP] Closing connection to 317319XXX.
When I try to open a secure channel to them, they see the very same
error message upon receiving the request (they are using OpenSSL 0.9.7e
-Udo.
signature.asc
Description: PGP signature
