Timeline for What strategies exist for decrypting and inspecting TLS 1.3 traffic?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 30, 2022 at 4:13 | answer | added | Sultan Omurzakov | timeline score: 0 | |
| Aug 5, 2021 at 14:26 | vote | accept | jester | ||
| Aug 3, 2021 at 20:35 | answer | added | Steffen Ullrich | timeline score: 3 | |
| Aug 3, 2021 at 19:57 | comment | added | jester |
@user10216038 The whole point of TLS is to prevent inspection of traffic. The past mechanisms you mentioned were techniques to subvert the security. Agreed 100%. I'm not trying to advocate for these strategies, I am simply contending that despite the goal of TLS being preventing snooping on protected traffic, it will still be done, just like it was in TLS 1.2 and prior. In trying to understand how it will be done, I'm asking this community if there is a mechanism that I'm missing.
|
|
| Aug 3, 2021 at 19:23 | comment | added | user10216038 | The whole point of TLS is to prevent inspection of traffic. The past mechanisms you mentioned were techniques to subvert the security. I suspect that the full proxy termination will remain the primary corporate mechanism. Forward Secrecy has been around for awhile now. The most common method used against Forward Secrecy is simply to capture the unencrypted traffic on the end-point devices. Authorized monitoring software does this, so too unauthorized malware. | |
| Aug 3, 2021 at 18:31 | history | edited | jester | CC BY-SA 4.0 |
added "and inspecting" to title
|
| Aug 3, 2021 at 18:00 | review | First posts | |||
| Aug 4, 2021 at 9:26 | |||||
| Aug 3, 2021 at 18:00 | history | asked | jester | CC BY-SA 4.0 |