[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2019-01-17 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 Peter Wu changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2018-10-31 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 Peter Wu changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2017-02-09 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 jochen.dar...@intel.com changed: What|Removed |Added CC||jochen.dar...@intel.com

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2017-01-05 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 David Bergeron changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2016-09-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 raysat...@yahoo.com changed: What|Removed |Added CC||raysat...@yahoo.com -- You

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2015-02-19 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 --- Comment #12 from Dirk d...@cubic.org --- I did not have the time to follow up on those initial suggestions. I also don't think that my employer will allow me to spend time on making changes to pcap-ng and then subsequently to Wireshark

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2015-02-17 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 --- Comment #9 from Anders Broman anders.bro...@ericsson.com --- (In reply to Peter Wu from comment #7) Can't find the mailing list discussion, did that happen? I have added a link to this bug on

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2015-02-17 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 Peter Wu pe...@lekensteyn.nl changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2015-02-17 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 --- Comment #10 from Alexis La Goutte alexis.lagou...@gmail.com --- (In reply to Peter Wu from comment #7) Can't find the mailing list discussion, did that happen? No found too The better is think, it launch discussion on pcap-ng

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2015-02-17 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 --- Comment #8 from Peter Wu pe...@lekensteyn.nl --- Forgot to mention this thing: For captures at https://git.lekensteyn.nl/peter/wireshark-notes/tree/tls, I am storing the session keys in the capture file comments. These lines begin

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2015-02-17 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 --- Comment #11 from Peter Wu pe...@lekensteyn.nl --- (In reply to Anders Broman from comment #9) And similar entry: http://wiki.wireshark.org/DecryptionBlock Saving the per-packet state seems complex, doing this just for the session

[Wireshark-bugs] [Bug 9616] use capture file comment to configure SSL dissector

2014-03-10 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9616 Hadriel Kaplan hadri...@yahoo.com changed: What|Removed |Added CC|