3 ms·
Yeah, let's just make it harder for banks to protect your money so that nobody can figure out your Facebook password in 10 years. EFF: "Everything sent over th
by peterwwillis 8y ago
Yeah, let's just make it harder for banks to protect your money so that nobody can figure out your Facebook password in 10 years.
EFF: "Everything sent over the network should be a secret! Nobody has a good reason to inspect traffic, it puts users' privacy at risk!"
Bank: "We keep trillions of your dollars. Inspecting our own traffic is how we make sure nobody is stealing it. We're a pretty big organization, so this stuff costs a lot of money, and is complex and takes a long time to get right. Can you give us a way to do that in this new TLS standard?"
EFF: "No!! Privacy!!!"
Bank: "Ok... I guess we'll have to make our own standard, then...?"
EFF: "Don't ANYONE use that standard, it will cause REAL HARM!!!!"
Bank: "..... Nobody else was going to... except us....."
- wolrah 8y agoPFS doesn't prevent inspection of traffic, it just makes passive capture more complicated since you now need to log the ephemeral keys for each connection rather than just using the private key to decode the whole package. Not necessarily trivial but not exactly impossible for someone who controls one of the endpoints. Active interception with a middlebox still works exactly the same as it always has.
- Dylan16807 8y ago> Nobody else was going to I doubt this pretty strongly. And if they can put in enough effort to implement a new protocol, they can put in enough effort to log some keys. They could do it in a much safer manner, too. They could have a TLS extension that appends the session key to the start of every connection, encrypted so that only the inspection device can use it. Then it would be transparent, connections not using it could be easily blocked, and you would still have forward secrecy in case the private key leaked.