RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2061725 - prefixdevname creates mislabeled files on boot
Summary: prefixdevname creates mislabeled files on boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: selinux-policy
Version: 9.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: 9.1
Assignee: Zdenek Pytela
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-08 12:18 UTC by David Tardon
Modified: 2022-11-15 12:56 UTC (History)
5 users (show)

Fixed In Version: selinux-policy-34.1.32-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 11:13:14 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github fedora-selinux selinux-policy pull 1184 0 None open Modify systemd_hwdb_manage_config() for named transition 2022-05-11 11:13:21 UTC
Red Hat Issue Tracker RHELPLAN-114803 0 None None None 2022-03-08 12:20:12 UTC
Red Hat Product Errata RHBA-2022:8283 0 None None None 2022-11-15 11:13:42 UTC

Description David Tardon 2022-03-08 12:18:35 UTC
This bug was initially created as a copy of Bug #2061680

Description of problem:
After a fresh RHEL 9.0 Beta installation and initial boot there is a mislabeled file created by prefixdevname present:

# restorecon -Rv /
Relabeled /etc/systemd/network/71-net-ifnames-prefix-net0.link from system_u:object_r:systemd_hwdb_etc_t:s0 to system_u:object_r:etc_t:s0

It would be nice to have the labels changed where needed so that restorecon wouldn't change anything. Thanks.

Version-Release number of selected component (if applicable):
RHEL 9.0 Beta

Comment 1 Michal Sekletar 2022-03-13 13:37:13 UTC
Default type is selected by the policy as "systemd_hwdb_etc_t" because of the following type transition,
type_transition udev_t etc_t:file systemd_hwdb_etc_t;

This essentially means that whenever udev (or whatever is forked-off by udev, e.g. prefixdevname) is creating a file in a directory labeled etc_t the resulting label will be systemd_hwdb_etc_t.
AFAICT, more generic label etc_t that is set by restorecon is just a result of default label inheritance, i.e. file inherits the label from the parent directory. I think the correct fix would be to adjust the type_transition and migrate it to named type transition, maybe something like this,
type_transition udev_t etc_t:file systemd_hwdb_etc_t hwdb.bin;

Comment 10 errata-xmlrpc 2022-11-15 11:13:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (selinux-policy bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8283


Note You need to log in before you can comment on or make changes to this bug.