https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12779
David Benjamin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #25 from David Benjamin <[email protected]> --- Regarding the SSLKEYLOGFILE format for BoringSSL in comment #17, we're open to changing the format if something else would be more convenient for you all. The current scheme was added just so you'd have something concrete to work. But this does seem the most natural thing to use in my opinion. The main thinking was that logging the traffic secrets means Wireshark doesn't have to maintain a handshake hash. (This would have been particularly annoying in earlier drafts with the resumption context.) Then the only bits you need to worry about are KeyUpdate and the key/IV derivation. https://tlswg.github.io/tls13-spec/#rfc.section.7.2 https://tlswg.github.io/tls13-spec/#rfc.section.7.3 (It also seemed better to only log what's needed for decryption and not, say, the resumption secret.) -- You are receiving this mail because: You are watching all bug changes.
___________________________________________________________________________ Sent via: Wireshark-bugs mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:[email protected]?subject=unsubscribe
