2 ms·
The model of security given in the article is a horrible way of implementing the principle of least privilege. A better way is set a reasonable set of resource
by mikewarot 5y ago
The model of security given in the article is a horrible way of implementing the principle of least privilege.
A better way is set a reasonable set of resources aside for the exclusive use of a given program (for storing state, etc.) and then using system dialog boxes to pick/choose other files/resources to work with. If done correctly, the user wouldn't even notice the difference in most cases.
A technical user could set up better defaults.
You're not going to get there using sandboxes on top of Linux, Windows, etc. Security has to be enforced in the OS kernel. I suspect eventually we'll end up using something like Fuchsia, Genode, Hurd, etc.
[Edit] It seems to me the composability aspect of unix needs to be re-interpreted in a way that allows composing of resources (capabilities) to be passed to a program. One could take a given resource and make it read-only for example. Email access that can only read a certain folder, or contacts, but never send, copy, etc. would be handy to be able to express. You could then pass that limited, specifically tailored set of things to a process with no other access to anything.