This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Actual path for system runtime files moved from /var/run to /run some 10 years ago , but the policy has been managed since then in a way that keeps the old entries and have updates still with the incorrect path while the real path is handled by file equivalency feature. This can confuse sysadmins not to be sure which path should be actually used and can also effect in userspace tools not working properly .
- Name: Zdenek Pytela
- Email: email@example.com
The change actually means just replacing “/run = /var/run” file-context equivalency rules with “/var/run = /run”. While the change as such is quite simple, it can have effect on other components using their own selinux policy with file-context entries.
Removing technical debt which originated 10 years ago. More straightforward handling of file-context entries in the /run filesystem.
- Add all relevant patches to upstream repository
- Ensure the system boots with the targeted policy
- Ensure the system boots with the mls policy
- Ensure updates from older releases work, more specifically with custom selinux packages installed.
- Developers of custom selinux policies need to confirm system updates work.
Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
Policies and guidelines: No update required.
Trademark approval: N/A (not needed for this Change)
Alignment with Objectives:
Users can be affected by this change if they use a local policy with file-context entries in /run which occurs quite rarely, but is possible.
- Install a new system and check for error messages and audit records.
- Update an existing system and check if all updates completed without an error.
- Optionally, install and boot the selinux-policy-mls package.
- Check for errors reported by dnf or rpm.
There should be no visible change for end users.
The change should be transparent, without any further action needed on the system. System admins may need to take an action based on compatibility with the changes.
Components with a custom selinux policy: container-selinux pcp cockpit
- Contingency mechanism: Revert all changes in case of serious problems with updates.
- Contingency deadline: 2024-02-06 (Branch Fedora Linux 40 from Rawhide)
- Blocks release? No
- Blocks product? No
To be added later.