Red Hat Bugzilla – Bug 578187
BIND 9.7 request - SELinux policy needs to be updated
Last modified: 2012-10-15 10:51:25 EDT
+++ This bug was initially created as a clone of Bug #570611 +++
Description of problem:
BIND 9.3 shipping with EL5 doesn't support NSEC3 and a number of other needed features. As EL5 will be around for some time in production, and EL6 is still forthcoming, BIND9.6 is needed for NSEC3 support. Specifically in the .GOV gTLD and others.
A tech preview of BIND 9.6 is requested for EL5.
--- Additional comment from firstname.lastname@example.org on 2010-03-05 04:44:31 EST ---
BIND 9.7 has been already released so I prefer to use it instead of older 9.6.
--- Additional comment from email@example.com on 2010-03-05 14:09:15 EST ---
Wonderful. Does another bug request need to be opened, or can this just be modified to ask for a tech preview of BIND 9.7?
BIND 9.7 tech preview will require to allow more actions in SELinux policy. I will prepare test package and attach list of rules which should be added.
After inspection following rule must be added to the policy:
allow named_t self:process getcap;
and /var/named/dynamic directory must be, by default, labelled as "system_u:object_r:named_cache_t", like /var/named/data and /var/named/slaves directory.
Fixed in selinux-policy-2.4.6-281.el5.noarch
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
A new version of Berkeley Internet Name Domain (BIND) required various additional changes in SELinux policy. These updated packages introduce the adjusted SELinux rules, and add the SELinux context for the /var/named/data/ and /var/named/slaves/ directories.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.