> But people still do it out of habit. It's very hard to come back from such a popular image of "100% broken and must be disabled immediately". Even if SELinux

> But people still do it out of habit. It's very hard to come back from such a popular image of "100% broken and must be disabled immediately". Even if SELinux evolves to absolute perfection, the damage to its image is done, and that will take a long time to change, regrettably. It should not have been shipped so green. > If you ignore SELinux, it won't cause issues besides the ocasional need to run "restorecon" (which one gets into the habit of doing whenever an "access denied" error happens when permissions seem otherwise correct). Sound like it's still pretty broken, IMHO. I should never see an "access denied" error on a host I control, unless I misconfigured it. The truth is, the defaults MUST work on all common scenarios all of the time for these things to be successful. Otherwise, people will only see the downsides (and the upsides are rarely visible, and rarely outweigh the downsides).