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.
Description of problem:
$ dnf install bind # do this first, separately
$ dnf install bind-dyndb-ldap
$ restorecon -Rvvn /etc/
Would relabel /etc/named.conf.bak from system_u:object_r:named_conf_t:s0 to system_u:object_r:etc_t:s0
Version-Release number of selected component (if applicable):
RHEL-9.0.0-20220108.3
bind-9.16.23-1.el9.x86_64
selinux-policy-34.1.20-1.el9.noarch
Additional information:
This happens because the postinst script of bind-dyndb-ldap seems to back up the config before rewriting it:
$ rpm --scripts -q bind-dyndb-ldap
postinstall scriptlet (using /bin/sh):
[ -f /etc/named.conf ] || exit 0
...
while read -r PATTERN
do
SEDSCRIPT+="$PATTERN"
done <<EOF
/^\s*dynamic-db/,/};/ {
...
}
EOF
sed -i.bak -e "$SEDSCRIPT" /etc/named.conf
This is actually a sed functionality I didn't know about - using the -i argument with a suffix, but the manpage does mention it.
selinux-policy cannot handle all backup file names.
Switching to the bind component to assess if the file can be kept with a label not matching the default file context database or if restorecon should be run.
Not really sure how to handle this issue. I think having backup with named_conf_t is correct. It would allow user to mv /etc/named.conf{.bak,} if it gone wrong. On the other hand I don't expect policy would match any common backup suffixes. Moving to bind-dyndb-ldap component to evaluate. Either call also restorecond on backup file or close it with WONTFIX.
Comment 7RHEL Program Management
2023-07-12 07:28:05 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Description of problem: $ dnf install bind # do this first, separately $ dnf install bind-dyndb-ldap $ restorecon -Rvvn /etc/ Would relabel /etc/named.conf.bak from system_u:object_r:named_conf_t:s0 to system_u:object_r:etc_t:s0 Version-Release number of selected component (if applicable): RHEL-9.0.0-20220108.3 bind-9.16.23-1.el9.x86_64 selinux-policy-34.1.20-1.el9.noarch Additional information: This happens because the postinst script of bind-dyndb-ldap seems to back up the config before rewriting it: $ rpm --scripts -q bind-dyndb-ldap postinstall scriptlet (using /bin/sh): [ -f /etc/named.conf ] || exit 0 ... while read -r PATTERN do SEDSCRIPT+="$PATTERN" done <<EOF /^\s*dynamic-db/,/};/ { ... } EOF sed -i.bak -e "$SEDSCRIPT" /etc/named.conf This is actually a sed functionality I didn't know about - using the -i argument with a suffix, but the manpage does mention it.