On Wed, Jan 24, 2024, at 14:51, Marten Seemann wrote: > That's an interesting idea. In principle it should be possible to only > export the header protection keys without exporting any other TLS keys. > I don't believe the SSLKEYLOGFILE has an option for that though, and > I'm not sure if there's a way to load header protection keys into > Wireshark.
It doesn't include that capability because it would be a QUIC thing and that is a TLS tool. It works for QUIC because it works for the parts of TLS that QUIC uses. That said, it would be possible, to share just the header protection secrets. They are trivially derived from the application traffic secrets, which could be discarded (if you were doing this as a post-processing step). Of course, the IETF balked at standardizing the file format, so that sort of feature is hard to manage. If you did this as a QUIC-specific thing, you could log the HP keys independent of the TLS ClientHello.random and instead create a log keyed by destination connection ID. It's annoying to have to do that, because you need to indirect through some other identifier - there is a many-to-many relationship involved - but it would be a more usable format.
