https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15708
--- Comment #5 from Peter Wu ---
Oh that option should certainly not be enabled, maybe we should print some
expert info when this condition is enabled. Or maybe just remove it, it can
only ever work for block ciphers and will break with
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15708
Youngje Kim changed:
What|Removed |Added
Resolution|--- |NOTABUG
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15708
--- Comment #4 from Youngje Kim ---
Hi. Peter.
I downloaded the same file again and opened it on another computer.
And I could not reproduce it.
I have compared the TCP, TLS, and HTTP2 options of both computers, there was a
difference
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15708
--- Comment #3 from Peter Wu ---
Hi Youngje,
I am unable to reproduce the issue with the attached capture.
Frames 443, 445, 447, 449, 451 and 453 seems to correspond with
frames 1445, 1447, 1449, 1451, 1453 and 1455.
Here, I see just
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15708
Alexis La Goutte changed:
What|Removed |Added
CC||alexis.lagou...@gmail.com,
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15708
--- Comment #1 from Youngje Kim ---
Created attachment 17070
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17070=edit
pcap
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15708
--- Comment #2 from Youngje Kim ---
Created attachment 17071
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17071=edit
sslkeylog
--
You are receiving this mail because:
You are watching all bug
