News for hackers. Stuff that matters.
Re:Support of OpenBSD pledge(2) in programming languages by sdkmvx on Saturday April 09, 2016 @05:52PM (#11463517)
OS X's libsandbox is much closer to SELinux. It's MAC-based (mandatory access control not Macintosh) and is actually TrustedBSD under the covers. Pledge simply disallows access to syscalls and paths outside a list. It's not very fine-grained. It also resets on exec, so it can't be used as a sandbox or container.
Re:Support of OpenBSD pledge(2) in programming languages by brynet on Saturday April 09, 2016 @06:05PM (#11463566)
The entire point of pledge is self-sandboxing, in the case of an exec promise the expectation is the new process will also self-sandbox.

If you think of a shell as an example, it will need to exec programs that do privileged things before they can drop them, but the parent shell itself may never need to say.. create sockets.

Re:Support of OpenBSD pledge(2) in programming languages by icebraining on Sunday April 10, 2016 @07:41AM (#11465787)
Unless it's Bash, with its /dev/tcp interface.