3 ms·
It's not a lack of professionalism that caused this. It's the abandoning of MULTICS and all that stems from that premature optimization. We've been nuts to run
by mikewarot 2y ago
It's not a lack of professionalism that caused this. It's the abandoning of MULTICS and all that stems from that premature optimization.
We've been nuts to run any systems based on Ambient Authority outside of a 1980s college classroom environment. Connecting everything via the Internet deranged us into a hellscape just waiting to emerge, as it does periodically.
You can't enumerate badness, as virus scanners try to do. Thus you have to TRUST all the code you run, which is nuts. Operating Systems should NEVER require that you trust code, especially mobile code (stuff that came from outside your 1980s college classroom).
We have fuses and circuit breakers, and all sorts of ways to limit the damage a short circuit can do, but no such analogs for limiting the scope of damage a chunk of code can do to the world. This is insane.
It's not the users, system admins, Microsoft, or anyone else. It's the security model underlying the OS. This problem was solved in the 1970s, for f*cks sake!
- slowmovintarget 2y ago> We have fuses and circuit breakers, and all sorts of ways to limit the damage a short circuit can do, but no such analogs for limiting the scope of damage a chunk of code can do to the world. This is insane. We have the exact thing for that. They're called virtual machines and containers where you have absolute control over the networking and disk access. You practically have to be a software developer to use them, but they exist. Most of us exchange convenience for security, however, so here we are.
- mikewarot 2y agoVirtual machines are the equivalent of plugging each appliance into it's own generator. It's a crude approximation of what should be trivial. It doesn't have to be this way. We don't have to trust anything outside of the microkernel of the OS.