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.
+++ This bug was initially created as a clone of Bug #1573998 +++
Description of problem:
Setsebool named_write_master_zones is permanently turned on when bind-dyndb-ldap is installed. It was required because home directory /var/named is not writeable by named daemon. This plugin requires /var/named/dyndb-ldap to be writeable by plugin. Mentioned setsebool is turned always off on uninstallation, which blocks change of default on that boolean. It would be changed on each uninstallation to non-default value.
Version-Release number of selected component (if applicable):
bind-dyndb-ldap-11.1-10.fc27
How reproducible:
always
Steps to Reproduce:
1. getsebool named_write_master_zones
2. dnf install bind-dyndb-ldap
3. getsebool named_write_master_zones
4. dnf remove bind-dyndb-ldap
5. getsebool named_write_master_zones
Actual results:
named_write_master_zones --> off
named_write_master_zones --> on
named_write_master_zones --> off
Expected results:
named_write_master_zones --> off
named_write_master_zones --> off
named_write_master_zones --> off
Additional info:
I think /var/named/dyndb-ldap directory should have label named_cache_t instead of named_zone_t.
With upcoming change, it should behave the same way, but this changing has to be removed. Once selinux-policy is changed, new package must conflict with previous policy. bind package would conflict also.