3 ms·
su "limited account" -c "questionable binary"?
by digi_owl 11y ago
su "limited account" -c "questionable binary"?
- detaro 11y agoA large value of app sandboxes are easy but controlled ways to allow exceptions. E.g.: an app can ask the sandbox for file access, the sandbox then prompts the user to select a file and only that file is then exposed to the app. Or even giving global access to functionality from a manifest file, without having to set up a restricted user/environment manually. (I wouldn't know without looking it up how to set up a linux user account that can't talk to the network. Or even better, only can talk to some part of the network.)
- digi_owl 11y agoReminds me of a friend of mine that when provided with a manual for how to do something "that's too complicated, please do it for me". Meaning that "containers" just becomes a wrapper for things that can already be done, if one just learn to do it rather than pointing and drooling (as someone once referred to the GUI as).
- detaro 11y agoWho needs restricted user permissions, you can just review the machine code of all your executables before running them ;)
- digi_owl 11y agohar har har...
- netheril96 11y agoDoing it for the humans is exactly the raison d'etre of software.
- digi_owl 11y agoYes and no. The problem is that the magic word "container" obscured what is actually being done (cgroups, namespaces, iptables, etc etc etc). Its one more thing that result in confusion between user and computer about the state of the machine.