3 ms·
Are there best practices for designing connected, secure-by-default embedded devices? If you want to give your fridge an IP address, I feel like there should be
by PhasmaFelis 11y ago
Are there best practices for designing connected, secure-by-default embedded devices? If you want to give your fridge an IP address, I feel like there should be an easy way to do that without additional security worries.
- xiphias 11y agoThere is no easy way. There are ways to prove software correctness, but it is far from easy
- TeMPOraL 11y agoAnd because you can only prove software to be correct given some specific conditions, your provably correct system will eventually get pwned through a side channel anyway.
- PhasmaFelis 11y agoI guess I'm thinking that, for a simple hardware system with a handful of inputs and a handful of outputs, there's no need for it to be able to support a full command line, various ports and protocols, etc, etc. There should be a setup where it is completely closed off by default, and the developer enables a few specific I/O channels that only interact with the logic the dev programmed in. I may be oversimplifying things. Or maybe I've just reinvented old-fashioned embedded circuits, which still work fine but are out of fashion because devs want to work with their familiar tools.