To be clear: SELinux is an important mitigation - just like the Windows Firewall - and one should not disable either.
To be clear: SELinux is an important mitigation - just like the Windows Firewall - and one should not disable either.
Sure, if you're messing around with k8s and doing fun eBPF stuff you are going to need to be careful. But for just installing an OS, running it to do some web-browsing, gaming, image editing, wordprocessing? I would be highly surprised if the defaults do not work.
I think we agree, and Fedora / Red Hat have done great work setting up great defaults.
But when a user encounters an issue with SELinux, the lack of feedback mechanisms to help them onto a better path results in them finding that advice.
(Me a as novice Linux user)
On some systems the avc violations also get printed in dmesg.
If violations block your whole system from even running, you can enable permissive mode, this only logs violations without enforcing them.
As others already mentioned, turning violation logs into allow rules can be done with audit2allow. Wouldn’t recommend blindly using that though as the generated rules are always either too narrow or too wide, just use it as a guideline.
From the top of my head, I don't know. But this might help: