Red Hat Bugzilla – Bug 216185
bind-chroot-admin able to change root mode 750
Last modified: 2013-04-30 19:34:41 EDT
Description of problem: I have a simlink in /var/named/chroot/var/named as "chroot -> /" (needed for ispconfig hosting control panel). When upgrading bind the rpm package runs /usr/sbin/bind-chroot-admin. This changes root perms to 750. bind-chroot-admin calls /bin/chmod and should use --preserve-root to prevent changing root. Version-Release number of selected component (if applicable): I first recognized this problem in bind-9.3.3-0.2.rc2.fc5 How reproducible: every time Steps to Reproduce: 1.Install bind less than 9.3.3-0.2.rc2.fc5 2.ln -s / /var/named/chroot/var/named 3.rpm -u bind-9.3.3-0.2.rc2.fc5.{machine}.rpm Actual results: Expected results: Additional info:
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