Bug 216185
Summary: | bind-chroot-admin able to change root mode 750 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joe Julian <joe> | ||||
Component: | bind | Assignee: | Adam Tkac <atkac> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5 | CC: | ovasik | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-05-02 16:52:50 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: | |||||||
Attachments: |
|
Description
Joe Julian
2006-11-17 17:30:52 UTC
Created attachment 141507 [details]
Patch to correct chmod not --preserve-root
Okay, I understand. But why do you use chroot linked to / ? Why don't you just remove the bind-chroot package? I think you'll get the same result... A simlink to root from /var/named/chroot/var/named/chroot when chrooted will allow the config files to point to /var/named/chroot/var/named and still find the data. The allows the admin scripts in ispconfig to work without modification. ie. "/var/named/chroot/var/named/chroot -> /" with chroot /var/named/chroot means that the simlink will point to the real /var/named/chroot allowing me to use the long directoryname within a chroot. My own opinion is that chmod should never be run without --preserve-root in config scripts unless you specifically need to change root. okay, added to CVS. Looks like fixed, closing |