News for hackers. Stuff that matters.
Re:Decrypting SSL at scale with eBPF, libbpf and K8s by josephcsible on Thursday August 11, 2022 @11:25AM (#32427170)
But don't the keys to decrypt the stream have to remain in memory for at least as long as the stream itself is active? Or is the issue that the connection completes too quickly, so that that doesn't give you enough time?
Re:Decrypting SSL at scale with eBPF, libbpf and K8s by fl_ciq on Thursday August 11, 2022 @12:19PM (#32427999)
The application keys definitely do. The handshake keys are modified and at some point become useless to tshark. Not sure if it is a defensive coding thing, or what, but yeah if we don't catch it at the exact right moment they don't work.
Re:Decrypting SSL at scale with eBPF, libbpf and K8s by josephcsible on Thursday August 11, 2022 @12:25PM (#32428099)
Okay, that makes sense. What do you need the handshake keys for, though? Aren't the application keys enough to decrypt all of the data that you need to?
Re:Decrypting SSL at scale with eBPF, libbpf and K8s by fl_ciq on Thursday August 11, 2022 @01:29PM (#32429086)
I think it's related to perfect forward secrecy. We used curl's SSLKEYLOGFILE environment variable to find out what tshark needed and then worked to reproduce what curl was producing.