5 ms·
Virtual fort knox would be impossible to secure. In the modern age, whether through stupidity or malice, those keys WOULD be stolen, leaked, breached, what have
by mrguyorama 7y ago
Virtual fort knox would be impossible to secure. In the modern age, whether through stupidity or malice, those keys WOULD be stolen, leaked, breached, what have you. Hell, the first time the US government tried this situation, the clipper chip, it was trivially bypassed and shown to be utterly broken by researchers
- aftbit 7y agoSure, Clipper was a disaster, but we've learned a lot about encryption since 1998. I still think key escrow and gov't backdoors are probably a bad idea, especially when you look at the US's privileged position in the internet, which should really be a global or jurisdiction-free space. However, I don't understand why it would be so much harder to protect these keys than the update signing keys that Apple, Google, Microsoft, etc (not to mention every app author including Facebook) already have to protect in order to prevent malicious actors (including nation states) from trivially bypassing all security protections by pushing a signed update to the end-user device. Honestly if your security model involves hiding from the FBI/NSA, you should not be using a cell phone to do your encryption/decryption. That device runs closed-source blobs and can be remotely configured, accessed, and updated by (at least) your carrier and the device manufacturer.
- sjy 7y agoDon’t Apple, Google and Microsoft already have keys that can be used to automatically update and backdoor any of the billions of devices running their OSes?
- tzs 7y agoMake it distributed. Have each phone generate a public/private key pair, and upload the public key to an anonymous repository. To escrow a key the client app uses a secret sharing system to generate 10000 key shares, with any 500 key shares being sufficient to reconstruct the escrow key. It encrypts each share with a randomly chosen public key from the anonymous repository. It sends these encrypted shares to the government. If the government wants to recover the escrow key, it has to make a public request for help in which it publishes the 10000 encrypted key shares. Have an app on the phone that can receive notification of such requests, and if it sees that your public key was used for one of the shares it asks you if you approve the government's request to recover the escrow key, and presents the government's argument in favor of this. If you approve, the app on your phone decrypts the share, encrypts it with a government key, and uploads it anonymously to the government. In effect, this system provides a jury of 10000 randomly chosen anonymous phone users to review the access request, and 500 of them have to approve in order for access to be granted.
- Supermancho 7y agoRelying on people who are actively using phones, to find time to make carefully consideted and measured judgements in the name of justice is ridiculous. Full stop.
- etaioinshrdlu 7y agoHas Apple, Google, or Microsoft ever lost the private key for signing code for delivery on devices? Not saying this is a good idea, but big tech seems to have figured out how to keep a number secret. This argument may not be very strong as a result.
- nitwit005 7y agoWindows update was subverted previously, but it was a man in the middle attack: https://www.wired.com/2013/03/flame-windows-update-copycat/ https://www.wired.com/2013/03/flame-windows-update-copycat/ ASUS did actually deliver a malicious update: https://www.vice.com/en_us/article/pan9wn/hackers-hijacked-asus-software-updates-to-install-backdoors-on-thousands-of-computers https://www.vice.com/en_us/article/pan9wn/hackers-hijacked-a...