Re:Stop Disabling SELinux: A Real-World Guide
by justanotherbody on Thursday February 02, 2017 @07:14PM
(#13556383)
Keep in mind there are a LOT of apps deployed on systems with SELinux with few, if any, tests
Further, the divide between ops and developers in many cases leaves this as an unsolvable problem - it's not the dev's job to do sysadmin, and ops lacks the expertise (or time) to comprehensively analyze the code base
You're right that this makes the app poorly behaved, but if that can't be addressed then... permissive mode it is
Re:Stop Disabling SELinux: A Real-World Guide
by snuxoll on Thursday February 02, 2017 @11:20PM
(#13557647)
Everyone keeps telling sysadmins they need to be able to write code, how about developers start learning more about how their applications are deployed.
I wear both hats, and then some more on top of that - if someone on my team is doing something that will make deployment and security difficult I make sure to nip it in the bud during testing.
audit2allow is a great tool for simplifying the development of SELinux policies, but it doesn't remove some hand-crafted modifications to policies, especially in regards to file contexts (fcontext).