2 ms·
I'm genuinely curious -- is there any empirical evidence to show that's the most effective approach? Because then the firmware can never auto-update, but needs
by crazygringo 5y ago
I'm genuinely curious -- is there any empirical evidence to show that's the most effective approach?
Because then the firmware can never auto-update, but needs to be manually and explicitly done -- flick the switch, apply the update, flick again.
And clearly a significant proportion of people (probably a very large majority if we're being honest) will simply never update firmware.
So which is the bigger threat: unpatched firmware, or firmware auto-update vulnerabilities?
The answer doesn't seem intuitively obvious at all to me. But there must be stats available -- frequencies and severities of vulnerability categories, and how often people update firmware on non-auto-updating devices. So it doesn't seem terribly hard to compute an answer?
- deleted 5y ago[deleted]
- bscphil 5y agoSplit the difference. Automatically update devices until they are end-of-lifed, then send a last update that blows a fuse allowing automatic updates. Anything after that point requires a write switch to be flipped. Actually, preferentially they should be taken offline and the consumer should have to opt-in to leaving them connected to the Internet, but that's a whole separate issue.
- crazygringo 5y agoI don't know, that doesn't seem like splitting the difference -- it seems like it might be the worst of both worlds. Before EOL auto-update is a vulnerability, and after EOL security patches might still be made available for the absolute worst vulnerabilities, but now wouldn't get to practically anyone.