3 ms·
The traditional fears are: 1. Subtle bugs that look OK during code review but actually introduce security problems (like == vs = but with a multi-billion-dolla
by michaelt 13y ago
The 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/