Red Hat Bugzilla – Bug 127555
named can't write slave zone files to /var/named/chroot/var/named/slaves
Last modified: 2007-11-30 17:10:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
The context associated with the slaves directory is incorrect, since
it doesn't allow bind to write zone files it downloads from master
servers in there. It has to be named_cache_t.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.start bind with a config file that requires slave zones to be stored
in the slaves dir, in the chroot
Actual Results: selinux won't let it.
Expected Results: it should.
Could you send me the AVC Messages?
Not easily. I ended up reinstalling FC3test1 with SELinux disabled on
all my boxes, because SELinux, as it stands, would take me too much
work to add file_contexts rules such that my home dir, that is a mess
of soft links, would work.
If you tried targeted policy there should not be a problem.
Homedirectories don't matter that much. But you could still generate
the bind error since it runs under policy.
This is now fixed.
The /var/named/chroot/named/slaves directory was not being created -
it now is, with ownership named:named, the same as the
/var/named/slaves directory, while /var/named and chroot/var/named
have ownership root:named.
This is now in bind-9.2.4rc6-1 in fc3-head.
I tried the targeted policy, it didn't work because I have stuff like
squid and sendmail writing to the partition that also contains my home
As for the contexts defined in the policy, it's still not right.
selinux-policy-*-1.15.9-1 define contexts for /var/named/slave, not
/var/named/slaves, both in root and chroot.
This is now fixed (selinux-policy-targeted-1.17.4-1 and
I've finally tried again an install of rawhide from scratch with
SELinux enabled, and I can now confirm that it works. Thanks,