6 ms·
Hooray simple security hacks! ....and booooo simple security hacks. In the previous thread, someone says "I really like this solution. Far better than pissing
by peterwwillis 11y ago
Hooray simple security hacks!
....and booooo simple security hacks.
In the previous thread, someone says "I really like this solution. Far better than pissing around with SELinux configuration and it's well contained." Which is a little bit like saying, "I really like these airbags. Way easier than using a seatbelt."
- pakled_engineer 11y agoOnly if the seat belt consists of thousands of strands you have to piece together, and if you screw up one strand your entire belt could fail. I've hung myself with SELinix a few times as complexity grows even just trying to set a policy(s) for an Android phone with half the features removed. Even the NSA guys on the SEAndroid mailing list have been stumped sometimes with complexity errors.
- vezzy-fnord 11y agoIt's actually a consistent mechanism for doing privilege dropping on a whitelist level. The same cannot be said for an API like POSIX capabilities.
- deleted 11y ago[deleted]
- JdeBP 11y agoMy initial reaction was that it didn't match my use. It doesn't seem possible to do what my use would require, which would be things like dropping specific identified privileges without affecting what other privileges the process might currently have. This would need some way for reading the process's current restrictions. The current API is write-only. Moreover none of the privilege sets seemed to allow the possibility of chain loading once privileges had been dropped, as none of them allow execve(). OpenBSD tame() is, as its blurb states, not designed with the model in mind of programs where initialization parts (consider UCSPI servers, for example) are in a separate executable that then chain loads through common privilege dropping tools to the main part of the program. It's not as easy to wrap tame() into some shell-level composable tool as it is to wrap jail() into the jexec tool.
- tyho 11y agoApart from SELinux is not available in OpenBSD, so you can't use both in tandem.