Hide Forgot
Description of problem: The bind and bind-chroot packages specs define and apply group ownership and permissions differently for the /usr/lib64/bind (chroot'd as /var/named/chroot/usr/lib64/bind) directory. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux 6.7 How to re-produce. # rpm -q --queryformat '%{NAME}:\n[%{FILEMODES:perms} %{FILEUSERNAME} %{FILEGROUPNAME} %{FILEFLAGS:fflags} %{FILENAMES}\n]' bind | grep lib64 drwxr-xr-x root root /usr/lib64/bind # rpm -q --queryformat '%{NAME}:\n[%{FILEMODES:perms} %{FILEUSERNAME} %{FILEGROUPNAME} %{FILEFLAGS:fflags} %{FILENAMES}\n]' bind-chroot | grep lib64 drwxr-x--- root named /var/named/chroot/usr/lib64/bind *** On disk ownership and permissions (matches bind-chroot specs) # ll /usr/lib64 | grep bind drwxr-x---. 2 root named 4096 Mar 9 16:05 bind *** The results of RPM validation (flagging because the bind specs do not match) # rpm -Va | grep '^.M' .M....G.. /usr/lib64/bind # rpm -Va | grep '^......G' .M....G.. /usr/lib64/bind Expected results: Same permission should not inherit.
When bind-chroot is installed, result of (sudo) rpm -V bind-chroot is different, when named service is stopped and when is started. Current version will pass check when stopped. service named stop rpm -V bind bind-chroot But fails after (successful) start service named start rpm -V bind bind-chroot Test case should include both cases.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0651.html