3 ms·
You could run your system completely in RAM, to at least limit the duration of exposure. Persistence is overrated! :)
by gen220 6y ago
You could run your system completely in RAM, to at least limit the duration of exposure.
Persistence is overrated! :)
- xaduha 6y agoYou're joking, but I don't think I will be running Windows without uwfmgr.exe aka Unified Write Filter if I ever decide to use it as my main OS again. More people should be aware of it. It's only for Enterprise editions, but maybe there are similar options out there.
- walterbell 6y agoOr a VM with snapshots / non-persistent storage.
- amelius 6y agoHow do you apply security updates?
- walterbell 6y agoImmediately after a clean boot, apply security update, reboot to test, then immediately shutdown and allow that snapshot to persist.
- amelius 6y agoWouldn't it be better to do a reinstall of the OS in the VM (or use a previous image), apply the security updates, and then reinstall any other software that was on the system?
- walterbell 6y agoTypically the base, non-persistent image is carefully managed to be pristine, e.g. through a tree of storage snapshots that allows reversion to known-good checkpoints.
- MichaelZuo 6y agoTo go one step further, have three, or more, identical fire walled systems running and have them vote on every calculation with the votes sent to a hardwired switch, that prevents the system from advancing if there’s a disagreement, and shuts off power to the RAM if there’s too many in a row. The chances of any compromise happening to all the systems within the same nanosecond would be infinitesimal.
- plasticchris 6y agoThey shouldn't be identical systems, common mode failures will get you.
- bboylen 6y agoFor anyone unfamiliar and curious, this is how the Tails OS works. https://tails.boum.org/ https://tails.boum.org/