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: Sun, 04 Sep 2016 20:53:16 +0000

Comment # 11 on bug 12793 from 
The concept "it is resumed unless ServerHello is present" is fine (Certificate
or ClientKeyExchabge also marks a full handshakes).

Using the most recent automated build shows 3 different results, depending on
the 2/Y/R options:

$ tshark -v | head -1
TShark (Wireshark) 2.3.0-542-g98b5820 (v2.3.0rc0-542-g98b5820 from master)
$ tshark -r Session_resumption.pcapng -Y ssl.resumed
  6   0.002285 192.168.12.2 → 192.168.12.12 TLSv1 197 Server Hello, Change
Cipher Spec, Finished
$ tshark -r Session_resumption.pcapng -2 -Y ssl.resumed
$ tshark -r Session_resumption.pcapng -2 -R ssl.resumed
  1   0.002285 192.168.12.2 → 192.168.12.12 TLSv1 197 Server Hello, Change
Cipher Spec, Finished
  2   0.019189 192.168.12.2 → 192.168.12.12 TLSv1 127 Change Cipher Spec,
Finished
$

No packets selected with ssl.resumed filter in the GUI.
Not the expected results.

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