Re:ETS Isn't TLS and You Shouldn't Use It
by KingMachiavelli on Tuesday February 26, 2019 @12:16PM
(#19256233)
Why? If you have the private key you can decrypt TLS traffic if forward secrecy is off. Which is why forward secrecy exists, to prevent captured encrypted sessions form being decrypted out-of-band with, presumably, comprimised private keys.
The issue is that TLS 1.3 deprecates the key exchange that makes this possible, essentially making (perfect) forward secrecy a requirement since the only inlcuded ciphers do so. The only way to monitor/inspect TLS traffic in this situation is to MITM the traffic rather than simply record encrypted sessions.
Re:ETS Isn't TLS and You Shouldn't Use It
by dcbadacd on Tuesday February 26, 2019 @01:24PM
(#19256919)
It's deceptive to call out-of-band MITM not MITM, it's still MITM just covert. TLSv1.3 forcing it to become glaringly obvious is exactly what should be happening.
Re:ETS Isn't TLS and You Shouldn't Use It
by aidenn0 on Tuesday February 26, 2019 @12:17PM
(#19256252)
For client-side it does require a new CA, but for server side it does not (since you have access to all of the private keys in use). Given that banks are pushing for this standard, that would make a lot of sense.
Re:ETS Isn't TLS and You Shouldn't Use It
by tonyarkles on Tuesday February 26, 2019 @12:13PM
(#19256208)
Correct re: the root cert in my experience at least. They usually get pushed out as part of a Group Policy in Active Directory.
And if you are in a corporate environment using a company computer you forfeit your privacy anyway. You can always go somewhere else or do your banking and Facebook on a different machine / not on company time.