2 ms·
The premise is wrong. It's like saying that we need to more carefully design the copper wires so that they don't touch anything accidentally, instead of... you
by mikewarot 3y ago
The premise is wrong. It's like saying that we need to more carefully design the copper wires so that they don't touch anything accidentally, instead of... you know... using insulators, and circuit protection.
You should be able to run any program you want, no matter who wrote it, nor the language used, safely. If you can't do that, your operating system sucks. Security is the operating system's job.
Just because we're collectively hotwiring everything to the computing grid, and just telling programmers, admins and users to be more careful, doesn't mean its a sane way to live.
To cope with our current insane situation, we've all discovered coping mechanisms, like putting things in VMs, Containers, using Sandboxes, etc... none of them are as effective as specifying at runtime exactly what side effects are allowed. The user can do it using powerboxes, the admin can do it in a batch file.
We can have easy to use, secure, general purpose computing, but at present, the Overton window is too far away for most people to see it as even possible.
I supposed it was like that with the electric grid at some point, too.
- l33t7332273 3y ago> Security is the operating system's job, not the application programmer. That’s just flat out not true. It’s jot possible for an operating system to be perfectly secure without unduly locking down the capabilities of applications.
- acuozzo 3y ago> Security is the operating system's job Considering the enormous feature-set of 1981's Intel iAPX 432, perhaps in 2023+ it should be the job of the hardware instead. Lisp Machine 2.0?