4 ms·
Here's my 30 second analysis Option A) What we have now Option B) Code in PROM with physical interlock (e.g. push button to enable write) Option C) Code in R
by aidenn0 9y ago
Here's my 30 second analysis
Option A) What we have now
Option B) Code in PROM with physical interlock (e.g. push button to enable write)
Option C) Code in ROM
Downsides of A are obvious, we see them now.
Downside of B is that automatic updates are impossible, so the majority of devices that are network connected will remain vulnerable. At the peak of code red, it took less than 5 minutes for a fresh windows install to be compromised.
You also will have people who will forget to disable the network before pushing the button, or who may be tricked into pushing the button which will allow malicious code to persist anyways.
C) Absent a hardware recall, people will just use devices that are infected within 5 minutes of bootup.
- WalterBright 9y ago> At the peak of code red This implies a lot of infected machines. As I mentioned earlier, machines getting uninfected at every reboot will reduce the number of infected machines at any point in time. It may reduce it far enough to provide "herd immunity", which is why we only need 90% of the population immunized against measles to prevent it from propagating. Furthermore, if people are aware that reboots will de-infect malware, machines can be set up to regularly reboot. For example, I could set up my router to reboot once an hour. This would be only a minor inconvenience, as it reboots pretty quickly. Regular reboot can be done by adding one of those simple hardware store lamp timers, or the device itself can contain a hardware circuit (outside of software control) to regularly reboot it. By the way, do your really want automatic updates to your disk drive firmware? Your USB stick firmware? I don't. They don't happen anyway, yet I've seen articles about how those get infected with malware.