Re:The hidden cost of QUIC and TOU (2016)
by hornetblack on Friday November 02, 2018 @03:35AM
(#18361232)
I know that for https in NSS browsers (Chrome and FF) you can dump the secrets to a file that Wireshark can read.
Given that Chrome is currently the biggest user i would be supprised if that was easy to update.
[ Parent
| on HN ]
Re:The hidden cost of QUIC and TOU (2016)
by nouseforaname on Friday November 02, 2018 @12:12PM
(#18364156)
I believe chrome currently uses BoringSSL not NSS, but still has some facilities for writing the same keylogfile.