On Thu, Jan 21, 2010 at 09:10:22AM -0800, Adam Langley wrote: > When developing Chrome, it's very useful to be able to use Wireshark > to look inside a TLS connection without having the server's key. I'm > sure other people have a similar issue with other programs.
Indeed, this has been discussed before and was on my wishlist for a while! > To this end, I'm asking for some lovin' for > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4349 My love for the request is still there :-) > The patch on that bug adds support for reading pre-master secret log > files generated by a TLS client (like Chrome). The NSS(*) side of this > patch has been r+'ed: > https://bugzilla.mozilla.org/show_bug.cgi?id=536474, but the Wireshark > bug has fallen silent for the past few weeks. Sorry for that, there is quite a bit of non-wireshark things that I need to take care of at the moment (I'm starting to work 100% for my own company at the first of February). I will take a look at the current status of the bug tonight or tomorrow... Cheers, Sake ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
