> Am 10.11.2025 um 17:22 schrieb Thomas Cameron via users > <[email protected]>: > > SELinux generally only throws errors if you're doing something unexpected.
That’s just one side of the coin. The other seems to be, that you do something expected and SELinux blocks unexpectedly. As an example, if you install Apache, SELinux thankfully grants access to ports 80/443 on the external interfaces by default. However, if you want to set up a reverse proxy and install e.g. Tomcat, SELinux blocks access to the port 8080 via localhost. This is intentional on the part of the maintainers, but unfortunately unexpected and inconsistent on the part of the sysadmin. There are many examples of this kind. And to make it even worse, documentation is non-existent or extremely difficult to find. And for quite some time now, Fedora's resources no longer seem to be sufficient for good SELinux support. Some software is not supported adequately. Time and again, I find that SELinux causes problems with software in Fedora, but works fine with SELinux-enabled Debian. In any case, even after 20 years, the situation with SELinux is not bad, but still unsatisfactory. Ultimately, this discourages users, causing them to switch to another distribution. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy [email protected] Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
