On Tue, 9 Sep 2003, Dann Daggett wrote: > resume [32]= > af ea 93 ad 17 8d d2 e7 9a 8d 7f a7 8f a0 8b 17 > 63 93 33 68 0d 43 99 94 b6 c9 dd e2 f8 17 3d 6f > NULL > 1 2 0.0056 (0.0043) S>C Handshake > ServerHello > Version 3.1 > session_id[32]= > af ea 93 ad 17 8d d2 e7 9a 8d 7f a7 8f a0 8b 17 > 63 93 33 68 0d 43 99 94 b6 c9 dd e2 f8 17 3d 6f
Looks like a resumed session.. please note that ssldump will get a bit confused unless it saw the initial handshake where the session was established. ssldump traces are best collected by first closing the browser or flushing the server session cache and works absoulutely best with session cache disabled (server setting). > cipherSuite TLS_RSA_WITH_RC4_128_MD5 > compressionMethod NULL > 1 3 0.0056 (0.0000) S>C ChangeCipherSpec > 1 4 0.0056 (0.0000) S>C Handshake > 1 5 0.0068 (0.0011) C>S ChangeCipherSpec > 1 6 0.0068 (0.0000) C>S Handshake > 1 0.0085 (0.0017) C>S TCP FIN > 1 0.0088 (0.0002) S>C TCP FIN Loooks very short to me.. client immediately closes the connection after the SSL connection is established. Total sessoin time (from SYN to FIN) only a fraction of a section (0.0088 seconds). Probably a broken client.. Try forcing the use of another ciphersuite in case the problem is the implementation of this specific cipher. Regards Henrik ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
