Hi, First of all the HEX line are important because they contained information about the connection (SSL protocol layer: record, alert etc...), in fact in acts as -msg option (openssl 0.9.7e).
In your case, it seemes that your server closed the connection: read from 080ABC00 [080B1838] (7 bytes => 0 (0x0)) The 7 bytes to be read sounds like an "error" message that should be read but is not. It seems that your server close the connection without sending anything. Which openssl do you use? Fred -----Original Message----- From: [EMAIL PROTECTED] on behalf of Hans Moser Sent: Wed 2/23/2005 4:14 PM To: openssl-users@openssl.org Cc: Subject: Re: s_client handshake failure [auf Viren überprüft] [EMAIL PROTECTED] schrieb das Folgende am 23.02.2005 12:09: > Hi, > > You can specify the protole to use with -ssl3 or -tls1 otherwise s_client > send a ssl v2 client hello. Moreover some debug info with -state or -debug > could be usefull to find what happened. ;) # openssl s_client -connect localhost:666 -showcerts -debug CONNECTED(000000003) write to 080ABC00 [080AC2D8] (142 bytes => 142 (0x8E)) .... 9 Lines of HEX read from 080ABC00 [080B1838] (7 bytes => 0 (0x0)) 4641:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib_c:226: with "-tls1" it changes only a bit into 4690:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s3_pkt.c:539: Hans ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
<<winmail.dat>>
