3 ms·
IMO it's not good that the kernel interferences keep on spawning endless userland "middleware" projects. I still want capsicum to give me sane defaults, so the
by Ericson2314 1y ago
IMO it's not good that the kernel interferences keep on spawning endless userland "middleware" projects.
I still want capsicum to give me sane defaults, so the incentive for sandbox security theater goes away.
- jeltz 1y agoSeems mostly off topic to the article. I think system containers should be implemented in user space. They are not about security theatre but about getting a sandboxed environment which feels like a real/virtual machine but is lighter weight. Very useful e.g. when I want to emulate a whole cluster of Linux machines. And for those needs security is nice but not key. It is application containers which maybe should be replaced by better kernel security, not system containers.
- Ericson2314 1y agoSo from the capsicum perspective, when you spawn a process, it should be maximally isolated by default. Any sharing of resources should be opt-in, not opt-out. This is not a big change implementation-wise, but it completely changes the programming model. Instead of dreaming up endless new sandboxing strategies, we just give processes exactly what they need, no more, no less.