Re:Support of OpenBSD pledge(2) in programming languages
by teamhappy on Sunday April 10, 2016 @08:46AM
(#11465910)
> [...] but it's a pity the unix world fragments yet again
> on something that should be trivial.
FWIW: Theo mentions in the talk that he's willing to change things if that makes it easier for other operating systems to adopt pledge(2).
Re:Support of OpenBSD pledge(2) in programming languages
by shirro on Monday April 11, 2016 @06:59AM
(#11470702)
The simplicity of the interface is what feels novel to me.
It probably isn't an issue with a project like Chrome or Firefox to find someone able to understand all the intricacies of seccomp-bpf and implement it properly. And I am sure seccomp is a much more powerful solution.
But for a sole programmer or small team writing some micro-services or similar it seems unlikely they are going to bother. By comparison sending a string with some well chosen categories looks so ridiculously easy it lowers the barriers a lot.
Perhaps the design of pledge will turn out to have advantages, but it's a pity the unix world fragments yet again on something that should be trivial. Either people will limit themselves to chroot as the only portable solution, or hairy libraries will be necessary (like libevent .. no, libev.. wait, libuv).