4 ms·
Make it a button, so the customer can apply updates, but they need to press a button to make it happen. Add another button which, using only software stored in
by mikeash 10y ago
Make it a button, so the customer can apply updates, but they need to press a button to make it happen. Add another button which, using only software stored in ROM, reloads the firmware from ROM. Then you have updates, but only when the customer knows and wants it, and if they ever screw it up then they can get back to a known good state.
- WalterBright 10y agoYup, that's the way to do it.
- Const-me 10y agoThe customer has no way of knowing whether they are installing genuine update, or MITM-modified malicious update. Public key cryptography solves that but then you have a problem how to protect the keys and crypto algorithms from tampering. Update buttons ain't a good replacement for TPM hardware.
- mikeash 10y agoIt's not a panacea, but nothing is, and it would help a lot. It's not supposed to be a replacement for anything, just an addition.
- WalterBright 10y agoIt's an enormously harder problem to convince the customer to push the "update firmware" button on the front panel than it is to insert malware remotely without any action or knowledge on the customer's part.
- Const-me 10y agoIt’s enormously easier problem to exploit a well-known remote code execution vulnerability, that’s unpatched because updates are too easy to ignore. For the end user, it’s extremely easy to NOT push that button.