3 ms·
Clearly we'll have to eliminate the dangerously transgressive TLS protocol from all .gov sites and let the mayhem ensue.
by kevin_thibedeau 3y ago
Clearly we'll have to eliminate the dangerously transgressive TLS protocol from all .gov sites and let the mayhem ensue.
- gruez 3y agoThe had a solution for that since the 90s: https://en.wikipedia.org/wiki/Clipper_chip https://en.wikipedia.org/wiki/Clipper_chip
- onesphere 3y agohttps://en.wikipedia.org/wiki/Crypto_Wars https://en.wikipedia.org/wiki/Crypto_Wars
- mindslight 3y agoThat is the banner from the last battle. TLS is exactly the type of centralizing protocol that these people now want - "security" that is fully contingent upon (ie vulnerable to) corporate middlemen and other centralized entities.
- aaomidi 3y agoCT literally exists.
- mindslight 3y agoComputed tomography? Certificate transparency? The Nutmeg State? None of these have anything to do with the main problem with TLS as commonly used, which is that servers are fully trusted.
- aaomidi 3y agoBut, that’s the objective of TLS? TLS isn’t a barrier to e2ee.
- mindslight 3y agoNeither is TCP or IP. But none of them are sufficient to provide user to user security. Bringing up TLS as if this bill is targeting it is missing the critical details of this new attack vector by our friendly geographical APT.
- quickthrower2 3y agoTLS is not end to end.
- immibis 3y agoIt is if you're doing it end-to-end. Don't remember which, but there are protocols where you directly connect to your recipient through the Tor network. Come to think of it, does anything stop you from running TLS over a messaging app? It only takes an extra 1-2 round trips at the beginning of the connection, right?