3 ms·
It's interesting to note that we essentially do the same with javascript in the browser, except the user doesn't even know there's some code that is automatical
by rakoo 12y ago
It's interesting to note that we essentially do the same with javascript in the browser, except the user doesn't even know there's some code that is automatically run.
The big difference, of course, being that javascript code runs in a sandboxed environment. Maybe we should create some kind of sandboxed sh ? (I actually hardly believe it will ever take on, seeing that so many sites tell you to run not `sh` but `sudo sh`... yeah, sure, why have unprivileged users, we should do everything as root anyway)
- paulmd 12y agoWell, the Unix approach to this is a sandbox application and a shell application, not a sandboxed shell application. Docker attempts many of those tasks. On windows there's Sandboxie, which does more or less what you want as well. It creates a sandbox whose filesystem and internals can be modified by sandboxed applications without affecting the state of the REAL filesystem. Very nice utility for mitigating bad programming - I often use it to run multiple copies of applications that crash or refuse to launch multiple instances.