Timeline for Limitations of TLS Inspection when using Diffie-Hellman
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2018 at 12:37 | vote | accept | Jausk | ||
| Feb 19, 2018 at 12:37 | comment | added | Jausk | You are right, perfectly clarified then! | |
| Feb 19, 2018 at 11:06 | comment | added | Steffen Ullrich | @user3194301: since your 2nd approach explicitly talked about re-encrypting the traffic for the server it is not the same as my third scenario. In this scenario the IDS only listens (passively) to the traffic and decrypts it for analysis, it does not infer with the end-to-end connection between client and server. | |
| Feb 19, 2018 at 10:21 | comment | added | Jausk | My 2nd Approach was intended to be in fact what you describe in your third scenario. As I suspected, you need to feed the IDS with information from the server in order to achieve a proper TLS Inspection when using DH. | |
| Feb 19, 2018 at 10:16 | history | answered | Steffen Ullrich | CC BY-SA 3.0 |