4 ms·
Pledge was not praised across the board for precisely the reasons you mention. It's optional so no one aiming for portability will implement it, it's not user c
by Spivak 10y ago
Pledge was not praised across the board for precisely the reasons you mention. It's optional so no one aiming for portability will implement it, it's not user configurable, permissions are too broad, it's unusable by any application that isn't pledge-aware, etc..
Now SELinux isn't perfect by any meaning, but the key difference is that applications can be SELinux aware if they choose, but you can still have full protection without the application knowing that it exists.
I would much rather try to improve SELinux than try to make pledge work for precisely this reason.
- Elhana 10y agoIt is also the reason why most common advice is to just turn off SELinux. It blocks valid (although sometimes weird) usage, because someone else decided that 90% of users should not do something. Developer knows better what program should and should not do and is much more capable to set this kind of rules with pledge.
- digi_owl 10y agoLets not forget that SELinux came out of the defensive side of NSA. Its to block attacks to government systems from both outside and inside. In essence it is the concept of "trusted computing" given form. And that concept in turn means that a general can put a trusted system into hostile territory and trust it to not leak secrets. And NSA still care for it. Around the time of the last kdbus dustup, someone from NSA voice a worry about how kdbus would compromise certain parts of SELinux.