Bug 187529
Summary: | bind update breaks permissions of local subdirectories of var/named | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | bind | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED ERRATA | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | joergen, redhat-tigerp |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | bind-9.3.2-16.FC5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-17 17:28:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexandre Oliva
2006-03-31 17:46:44 UTC
A possible work around for this problem is to copy all the own zone files from the master directory to the named directory (one level up) and edit the named.conf to reflect those changes. Sorry about that - the next update (bind-9.3.2-16.FC5+) will not change permissions of any $ROOTDIR/var/named/ directory other than slaves/ or data/. NOTE: you are confusing the named SELinux policy by putting your master files in a subdirectory of $ROOTDIR/var/named/ - why not work with the policy by moving your zone files to $ROOTDIR/var/named/ ? Thanks. The reason is that I keep the zone files in CVS, and IIRC at some point CVS didn't like the fact that the directory I checked files into already existed, or already contained files, or had extraneous permissions or some such. When slaves was introduced, I thought that was a good idea and started using masters/ myself :-) At that time, it worked fine with SELinux. Nowadays, I haven't been able to use SELinux in enforcing mode for other reasons (still haven't figured out how to customize policies for local needs yet, after the revamp that removed local.te :-), so I haven't got to adjusting named as needed. That said, AFAICT, the directories and files are labeled correctly, so it looks like it's going to work. This bug is now fixed with bind-9.3.2-16.FC5, shortly to be released to FC-5 Updates/Testing. bind-9.3.2-16.FC5 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. bind-9.3.2-16.FC5 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. Looks good to me, thanks! Sorry about the slow response. The bind installation in FC5 (upgrade from FXC3) messed up all the file permissions in /var/named. Furthermore bind was installed although it was not installed according to RPM and destroyed my custom installation of bind. |