Changes to SELinux
Review the most notable changes to SELinux between RHEL 9 and RHEL 10.
- Seven additional RHEL services transition to SELinux enforcing mode
-
Starting with RHEL 10.3, the following SELinux domains move from permissive to enforcing mode:
- powerprofiles_t
- qgs_t
- redfish_finder_t
- sshd_auth_t
- sshd_session_t
- systemd_mountfsd_t
- systemd_oomd_t
As a result, the system proactively prevents unauthorized access for these services.
- SELinux confinement for the
go-fdo-serverservices -
Starting with RHEL 10.3, SELinux confines the systemd services that the
go-fdo-serverpackage provides. To run these services in the correct context without SELinux denials, you must use the provided systemd units and install the latestselinux-policybuild.
- SELinux file context equivalency for
/var/optoverrides custom rules during system upgrades -
Starting with RHEL 10.2, the SELinux policy treats the
/var/optpath as equivalent to the/optpath. Because equivalency rules take priority over explicit paths, with this update, files under/var/optinherit default/optsecurity contexts, such asusr_t.This change impacts systems upgraded from earlier RHEL releases. Custom or third-party file context rules defined directly for
/var/optare ignored after upgrading to RHEL 10.2. As a result, applications or utilities, such aslogrotateor monitoring agents, that rely on custom contexts under/var/opt, might encounter SELinux denials or service failures.To set custom SELinux contexts for specific subdirectories under
/var/opt, define localfcontextrules for the corresponding/optdirectory structure, then apply the changes on the corresponding/var/optdirectory structure by using therestoreconcommand:# semanage fcontext -a -t <context_type> "/opt/<directory>(/.*)?" # restorecon -R -v /var/opt/<directory> - SELinux policy modules related to EPEL packages moved to
-extrasubpackages in the CRB repository -
In RHEL 10.0, the SELinux policy modules related only to packages contained in the Extra Packages for Enterprise Linux (EPEL) repository and not to any RHEL package were moved from the
selinux-policypackage to theselinux-policy-epelpackage. This reduced the size ofselinux-policy, allowing the system to perform operations such as rebuilding and loading the SELinux policy faster.In RHEL 10.1, the modules from
selinux-policy-epelare moved to the following-extrasubpackages in the RHEL CodeReady Linux Builder (CRB) repository:-
selinux-policy-targeted-extra -
selinux-policy-mls-extra
This change enables the automatic installation of
-extraSELinux policy modules when users enable the EPEL repository. -
rpm -qlreturns incorrect location of theselinux-policypackages on RHEL in image mode- The
rpm -qlcommand lists non-existent locations of theselinux-policyandselinux-policy-targetedwhen used on RHEL in image mode. The policy modules are installed in the/etc/selinux/targetedinstead of/var/lib/selinux/targeteddirectory, as misleadingly reported byrpm. This discrepancy is expected because most file systems in image mode are read-only, and the RPM tool doesn’t have the actual location of installed packages.