4 ms·
This is about OpenBSD pledge(2), which was designed to allow developers to write software that can be sandboxed, not as a mechanism to sandbox arbitrary softwar
by notaplumber 9y ago
This is about OpenBSD pledge(2), which was designed to allow developers to write software that can be sandboxed, not as a mechanism to sandbox arbitrary software with requirements for which you don't fully understand.
http://man.openbsd.org/pledge http://man.openbsd.org/pledge
- protomyth 9y agoWell, the article actually attempts to use pledge to do just that. This results in a nice article that teaches a bit about pledge, sandboxing, and ktrace. The conclusion does explain why pledge would be a poor generic sandbox. This point has been made from the early days, but I think this exercise reinforces it, that pledge works best with programs where you understand what the program is doing. A generic pledge wrapper isn’t of much use because the program is going to do something unexpected and you’re going to have a hard time wrangling it into submission.
- notaplumber 9y agoSorry, this was more for HN readers benefit. I know he's writing this from a developers perspective.
- sbierwagen 9y agoIndeed Ted probably knows that, since he's been an openbsd developer for 13 years.