4 ms·
I disagree. Isolating this on a separate piece of hardware might be a good idea. But getting your code on the hardware seems like an obvious and fairly fatal f
by joe_the_user 13y ago
I disagree.
Isolating this on a separate piece of hardware might be a good idea. But getting your code on the hardware seems like an obvious and fairly fatal flaw. The possibility of the NSA forcing the single maker to insert some hidden code or even some hidden extra hardware makes this a "single point of failure". They sell servers the size of "wall-warts" - you could run Linux or BSD on that and run your secure email on top of that.
Keeping a general purpose computer secure is always going to be a problem but recent experience seems to pretty say "if you can't trust yourself, you can't trust anyone".
- SimonJester89 13y agoIf their stuff is open-source how will they hide backdoors even if forced to insert them? I don't get it.
- arthulia 13y agoOnly the software is open source, the hardware could still be backdoored. Not to mention unless you plan on compiling the software yourself and installing it on the box, there is no way to be sure that is what you're really getting. I am not too paranoid about that kind of thing being true but I'm also not that excited about this device.
- michaelt 13y agoThe traditional fears are: 1. Subtle bugs that look OK during code review but actually introduce security problems (like == vs = but with a multi-billion-dollar spy agency behind it). 2. Binaries that don't match the source code (compile with the backdoor present, release code with it removed). 2b. An auto-update mechanism that lets the vendor deploy an update only you receive, which compromises your keys, then releasing another update minutes later which removes the compromise and covers their tracks. 3. The device shipping with an update mechanism that adds a backdoor during update installation, so there's no backdoor when you inspect the update on your computer but there is when running on the device. [1] http://underhanded.xcott.com/ http://underhanded.xcott.com/
- marbu 13y agoYes, having open-source software is a requirement in this case, but it's hardly the whole story.
- marbu 13y agoI see your point. But if this is a viable idea, the competitors with similar solution will appear eventually, which would sort of remove the single point of failure. On the other hand if this fails, nobody will try to get there a nasty backdoor. Moreover compared to the current state when almost nobody uses gpg because it doesn't work with their favourite cloud provider, this approach would provide a nice alternative.