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...
Recently a supplier of ours announced that we could finally host their shitty java app on Linux instead of paying fucking Oracle for Solaris. So we were eager to hear the requirements. It was RHEL 8.4 or something, a version that was already EOL at the time.
SELinux has long suffered from usability issues. Many commercial software packages require SELinux be disabled.
Fix the docs, improve error messages, and create a GUI to improve usage.
deleted by creator
I agree, but I don’t expect software companies to support it without clear documentation.
deleted by creator
Recently a supplier of ours announced that we could finally host their shitty java app on Linux instead of paying fucking Oracle for Solaris. So we were eager to hear the requirements. It was RHEL 8.4 or something, a version that was already EOL at the time.
They can’t even update their distros apparently.
Hate to be the type of person to comment this, but patches more than welcome
for real though, even a small contribution to the docs helps a ton