https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
Peter Wu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|IN_PROGRESS
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #18 from Gerrit Code Review ---
Change 32857 merged by Peter Wu:
TLS: Implement reassembly for Handshake messages
https://code.wireshark.org/review/32857
--
You are receiving this mail because:
You are watching all bug chang
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #17 from Gerrit Code Review ---
Change 32950 had a related patch set uploaded by Peter Wu:
packet: ensure pinfo->curr_layer_num does not depend on tree
https://code.wireshark.org/review/32950
--
You are receiving this mail b
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #16 from Gerrit Code Review ---
Change 32949 had a related patch set uploaded by Peter Wu:
packet: ensure pinfo->curr_layer_num does not depend on tree
https://code.wireshark.org/review/32949
--
You are receiving this mail b
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #15 from Gerrit Code Review ---
Change 32919 had a related patch set uploaded by Peter Wu:
packet: ensure pinfo->curr_layer_num does not depend on tree
https://code.wireshark.org/review/32919
--
You are receiving this mail b
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #14 from Peter Wu ---
More details on why the issue occurs:
Frame 25 contains two TLS layers due to TCP reassembly:
- The start of the TCP segment completes reassembly of a previous TLS record.
- The remaining part is also a
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #13 from Peter Wu ---
Found the culprit for the difference in pinfo->curr_layer_num. Commit
v2.5.0rc0-1206-gcd90f732a1 tried to cleanup the frame.protocols field by
removing items when the dissector did not add any item.
The p
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
Peter Wu changed:
What|Removed |Added
Status|CONFIRMED |IN_PROGRESS
--
You are receiving this
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #11 from Gerrit Code Review ---
Change 32857 had a related patch set uploaded by Peter Wu:
[WIP] TLS: Implement reassembly for Handshake messages
https://code.wireshark.org/review/32857
--
You are receiving this mail because
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #12 from Peter Wu ---
The following observation is with version 1 of the above patch applied:
TODO something is not entirely right with the capture from bug 15625
(attachment 17011), Frame 25. It contains a large Certificate R
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
Peter Wu changed:
What|Removed |Added
See Also||https://bugs.wireshark.org/
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #9 from Bob ---
on-call this week but will try to find a time to back off to 2.2 and export
session keys.
--
You are receiving this mail because:
You are watching all bug changes.__
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #8 from Bob ---
Created attachment 17011
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17011&action=edit
Trace file up SYN-to-Encryption Handshake
Can not give out the private key.
--
You are receiving this mai
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #7 from Peter Wu ---
Created attachment 17009
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17009&action=edit
RSA private key for attachment 17008
This is the test private RSA key for attachment 17008.
Bob, coul
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #6 from Peter Wu ---
Created attachment 17008
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17008&action=edit
TLS 1.2 AES-SHA256 with mutual authentication and EMS
I was unable to reproduce the decryption issue w
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #5 from Peter Wu ---
(In reply to Alexis La Goutte from comment #4)
> (In reply to Bob from comment #3)
> > Created attachment 17004 [details]
> > Screen shots of the issue
>
> Hi,
>
> Please attach PCAP (and key)
Given the
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #4 from Alexis La Goutte ---
(In reply to Bob from comment #3)
> Created attachment 17004 [details]
> Screen shots of the issue
Hi,
Please attach PCAP (and key)
--
You are receiving this mail because:
You are watching all b
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #3 from Bob ---
Created attachment 17004
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17004&action=edit
Screen shots of the issue
--
You are receiving this mail because:
You are watching all bug changes.___
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
--- Comment #2 from Peter Wu ---
I am unable to reproduce the issue with the capture from bug 14243 either,
attachment 15976 (capture file) and attachment 15977 (RSA private key).
Neither can I reproduce it with a key log file generated fr
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
Peter Wu changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15625
Alexis La Goutte changed:
What|Removed |Added
CC||alexis.lagou...@gmail.com,
21 matches
Mail list logo
