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 GUI use cases (this topic is focused on desktop use cases, not server, infra, and such). By default, SELinux does not enforce much within user accounts but only around them. But in graphical desktop...
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.
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.
Nothing will make your system magically more secure, but SELinux is of great help when properly set up (as is in the case of Fedora).