4 ms·
> But almost no one needs to write a policy. But that's exactly what I would like to do! I've never seen a real guide for how to set up a policy for a custom d
by noinsight 2y ago
> But almost no one needs to write a policy.
But that's exactly what I would like to do! I've never seen a real guide for how to set up a policy for a custom daemon I wrote myself. Or when a specific software doesn't come with a policy.
- CrLf 2y agoIt's true that there is a lack of simplified documentation. But that lack is also the result of the folks that would otherwise contribute to such documentation not even giving SELinux a chance. Many years ago I decided to face the Bogeyman and went from knowing very little about SELinux to writing a policy from scratch in about a month. The policy is simple enough (but realistic) that it might help in the absence of a guide: https://github.com/carlosefr/kyoto/tree/master/selinux https://github.com/carlosefr/kyoto/tree/master/selinux I used it as an example in a couple of talks, whose slides might also provide additional context: https://github.com/carlosefr/public-talks/blob/master/presentations/selinux_en_campfire_2017.pdf https://github.com/carlosefr/public-talks/blob/master/presen...