Mathias Stearn wrote:
There is a reason the number one question for SELinux is how to turn
it off. It brakes a lot of things and its not easy for the user to fix
it. Unfortunately there is money in managing the problem but not in
fixing it.
--Mathias
Back in the day people would chmod their files to 777 because they
didn't understand file permissions. They just needed education -- same
thing for SELinux.
Most distros now ship with pre-defined policies on applications, I've
yet to really see someone have a *need* to turn it off. They just
didn't know where/how to troubleshoot their problem.
