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-server services

Starting with RHEL 10.3, SELinux confines the systemd services that the go-fdo-server package provides. To run these services in the correct context without SELinux denials, you must use the provided systemd units and install the latest selinux-policy build.

SELinux file context equivalency for /var/opt overrides custom rules during system upgrades

Starting with RHEL 10.2, the SELinux policy treats the /var/opt path as equivalent to the /opt path. Because equivalency rules take priority over explicit paths, with this update, files under /var/opt inherit default /opt security contexts, such as usr_t.

This change impacts systems upgraded from earlier RHEL releases. Custom or third-party file context rules defined directly for /var/opt are ignored after upgrading to RHEL 10.2. As a result, applications or utilities, such as logrotate or 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 local fcontext rules for the corresponding /opt directory structure, then apply the changes on the corresponding /var/opt directory structure by using the restorecon command:

# semanage fcontext -a -t <context_type> "/opt/<directory>(/.*)?"
# restorecon -R -v /var/opt/<directory>
SELinux policy modules related to EPEL packages moved to -extra subpackages 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-policy package to the selinux-policy-epel package. This reduced the size of selinux-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-epel are moved to the following -extra subpackages in the RHEL CodeReady Linux Builder (CRB) repository:

  • selinux-policy-targeted-extra
  • selinux-policy-mls-extra

This change enables the automatic installation of -extra SELinux policy modules when users enable the EPEL repository.

rpm -ql returns incorrect location of the selinux-policy packages on RHEL in image mode
The rpm -ql command lists non-existent locations of the selinux-policy and selinux-policy-targeted when used on RHEL in image mode. The policy modules are installed in the /etc/selinux/targeted instead of /var/lib/selinux/targeted directory, as misleadingly reported by rpm. 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.