Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Same behavior described below on RHELAH 7.3.3
# find /sysroot -context '*:default_t:*'
/sysroot/ostree/deploy/rhel-atomic-host/deploy/bfc591ba1a4395c6b8e54d34964b05df4a61e0d82d20cc1a2fd817855c7e2da5.0/sysroot
# atomic host status
State: idle
Deployments:
● rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
Version: 7.3.3 (2017-02-27 16:31:38)
Commit: bfc591ba1a4395c6b8e54d34964b05df4a61e0d82d20cc1a2fd817855c7e2da5
OSName: rhel-atomic-host
# rpm -q selinux-policy selinux-policy-targeted
selinux-policy-3.13.1-102.el7_3.15.noarch
selinux-policy-targeted-3.13.1-102.el7_3.15.noarch
+++ This bug was initially created as a clone of Bug #1428109 +++
On F25 Atomic Host, I was poking around looking for anything that matched the 'default_t' label and found the following:
# find /sysroot -context '*default_t*'
/sysroot/ostree/deploy/fedora-atomic/deploy/c5c811e10db838e848117f3e73b32a489b2c79ac2b86da87866b37c0fa7d135a.0/sysroot
/sysroot/ostree/deploy/fedora-atomic/deploy/5a0df79bd7225775231ea560615fc2ee2427c02d2904c1f0c6f292b4659d4cfa.0/sysroot
It's my understanding that we generally don't want files/dirs to have the 'default_t' label.
# atomic host status
State: idle
Deployments:
● fedora-atomic:fedora-atomic/25/x86_64/updates/docker-host
Version: 25.66 (2017-02-27 03:57:25)
Commit: 5a0df79bd7225775231ea560615fc2ee2427c02d2904c1f0c6f292b4659d4cfa
OSName: fedora-atomic
# rpm -q selinux-policy selinux-policy-targeted
selinux-policy-3.13.1-225.10.fc25.noarch
selinux-policy-targeted-3.13.1-225.10.fc25.noarch
--- Additional comment from Colin Walters on 2017-03-01 14:48:44 EST ---
On current CentOS AH, it's `root_t`, which I think makes sense.
It's not actively breaking anything - we could go to the EOL of RHEL7 with this bug. But it'd be nice to fix, since we'd like to have a check that no files are labeled default_t.
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, 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-2017:1861
Same behavior described below on RHELAH 7.3.3 # find /sysroot -context '*:default_t:*' /sysroot/ostree/deploy/rhel-atomic-host/deploy/bfc591ba1a4395c6b8e54d34964b05df4a61e0d82d20cc1a2fd817855c7e2da5.0/sysroot # atomic host status State: idle Deployments: ● rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard Version: 7.3.3 (2017-02-27 16:31:38) Commit: bfc591ba1a4395c6b8e54d34964b05df4a61e0d82d20cc1a2fd817855c7e2da5 OSName: rhel-atomic-host # rpm -q selinux-policy selinux-policy-targeted selinux-policy-3.13.1-102.el7_3.15.noarch selinux-policy-targeted-3.13.1-102.el7_3.15.noarch +++ This bug was initially created as a clone of Bug #1428109 +++ On F25 Atomic Host, I was poking around looking for anything that matched the 'default_t' label and found the following: # find /sysroot -context '*default_t*' /sysroot/ostree/deploy/fedora-atomic/deploy/c5c811e10db838e848117f3e73b32a489b2c79ac2b86da87866b37c0fa7d135a.0/sysroot /sysroot/ostree/deploy/fedora-atomic/deploy/5a0df79bd7225775231ea560615fc2ee2427c02d2904c1f0c6f292b4659d4cfa.0/sysroot It's my understanding that we generally don't want files/dirs to have the 'default_t' label. # atomic host status State: idle Deployments: ● fedora-atomic:fedora-atomic/25/x86_64/updates/docker-host Version: 25.66 (2017-02-27 03:57:25) Commit: 5a0df79bd7225775231ea560615fc2ee2427c02d2904c1f0c6f292b4659d4cfa OSName: fedora-atomic # rpm -q selinux-policy selinux-policy-targeted selinux-policy-3.13.1-225.10.fc25.noarch selinux-policy-targeted-3.13.1-225.10.fc25.noarch --- Additional comment from Colin Walters on 2017-03-01 14:48:44 EST --- On current CentOS AH, it's `root_t`, which I think makes sense.