Wireshark-bugs: [Wireshark-bugs] [Bug 12793] Expert Info ssl.resumed incorrect after TLS renegot
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 31 Aug 2016 10:18:11 +0000

Comment # 4 on bug 12793 from 
Opening the attached pcap in nightly build version 2.3.0-496-g6362183 both
handshakes are flagged as NOT resumed. The display filter "ssl.resumed" now
filters zero packets in the GUI.
This is not correct. The first handshake (frame 6) is resumed, the second
(frame 57) is not.

Snippet from the SSL debug log:

Wireshark version: 2.3.0-496-g6362183 (v2.3.0rc0-496-g6362183 from master)
GnuTLS version:    3.2.15
Libgcrypt version: 1.6.2
...
dissect_ssl enter frame #6 (first time)
...
ssl_dissect_change_cipher_spec Session resumption using Session ID
...
dissect_ssl enter frame #57 (first time)
...
ssl_dissect_change_cipher_spec Not using Session resumption

A single TCP stream can contain multiple SSL handshakes / renegotiations --
triggered by a "Handshake Type: Hello Request (0)" -- and may need multiple ssl
decoders.

You are receiving this mail because:
  • You are watching all bug changes.