SELinux provides a strong security measure that can make an SELinux-enabled operating system a type of “fortress”: the so-called “confined users” [1] [2] [3], which add security and isolation capabilities that are in several respects comparable to containers but without many of their restrictions in...
I'm not aware of another one. Some other distros like Ubuntu and OpenSUSE ship AppArmor instead, which does similar things but isn't considered quite as secure.
I know plenty of other popular distros don't ship any Mandatory Access Control system at all which seems like a very bad security practice to me. Same thing with Firewalls.
Nitpick: it's not that AppArmor isn't as secure, it's just that SELinux is more powerful. The security always is up to the profiles.
If you were to compare the policies for Fedora and e.g. Debian, I would assume Fedora has better ones though lol
yeah, same. I am currently on NixOS, but looking to move away because it's lacking support any MAC. I really love NixOS and it's declarative approach to things, but i can't live with such a large security hole in my home Network.
As soon as i find a Distro that has MAC and allows for at least semi-declarative configuration, i am switching. But being able to declare an env/dconf setting in my config and sync it across all devices is just too powerful
SELinux will not magically make your system more secure. Desktop insecurity mostly boils down to poor user choices. E.g Granting vscode full access to your home folder and installing some random extension.
Flatpaks and similar "container" tools are the obvious tools to use if you care about desktop security which the Linux ecosystem still generally deems as a lesser priority over being able to gain "rootful" permissions to carry out administrative tasks.
Seriously, I didn't know jack about SELinux before joining the SIG and now I know a little less than jack about it (I tried confining my user and managed to be unable to login to my system)
You can just take a look at the links in the thread if you want to start testing, and can help report issues with your experiences in our Pagure repo, I still need to report mine to mnow if it's a thing with GDM or if I just did something wrong
A bit dated experience, but I wanted to make a 'simple' web app (nginx/fpm/psql) SELinux compatible in 2014.
After reading the docs, it seemed I needed three layers of configuration just to make a policy. For two ports and two folders, that seemed way too complicated and absolutely not worth it.
I love it and it really makes my Desktop more secure. Switching it off, has lead to installing hostile or insecure software within months. When it was introduced, i felt controlled by it, but actually i saw, what a mess came out of it when i disabled that. Today i feel protected, out of eperience, even if i know shirt about how it exacly works, but i saw stupid software harming my system when it was disabled.
The "many eyes" theory is dead since the NSA backdoor in OpenSSL clearly showed how delusional that belief is. SELinux has never been audited by any trustworthy truly US-independent entity, making it nearly as untrustworthy as closed source. On top of that, there is always The Underhanded C Contest, proving that looking at the source is not enough. You need to be an expert who can detect underhanded backdoors too. – Evi1M4chine Feb 3, 2018 at 13:05