Red Hat Bugzilla – Bug 14350
incorrect file and directory permissions (reported by linuxconf)
Last modified: 2008-05-01 11:37:56 EDT
3 files and 1 directory are installed with incorrect permissions (at least they don't
match what linuxconf thinks they should be.)
After a fresh beta3 installation, reboot and run linuxconf.
Don't change anything, just quit linuxconf and look at the
changes it wants to make.
Here are the files BEFORE running Linuxconf:
-rw------- 1 root root 603 Jul 7 12:15 /etc/shadow
-r-sr-xr-x 1 root root 372340 Jul 4 01:16 /usr/sbin/sendmail
drwxr-xr-x 2 root mail 4096 Jul 7 12:27 /var/spool/mqueue
-rwxr-xr-x 1 root root 143676 Jun 5 15:51 /usr/sbin/pppd
First time run of linuxconf after installation says:
Changing permissions of file /etc/shadow from 100600 to 100400
Changing permissions of file /usr/sbin/sendmail from 104555 to 106755
Changing owner of file /var/spool/mqueue to root.root
Changing permissions of file /usr/sbin/pppd from 100755 to 104755
Changing owner of file /var/spool/uucp to uucp.root
AFTER linuxconf applies the changes:
-r-------- 1 root root 603 Jul 7 12:15 /etc/shadow
-rwsr-sr-x 1 root root 372340 Jul 4 01:16 /usr/sbin/sendmail
drwxr-xr-x 2 root root 4096 Jul 7 12:27 /var/spool/mqueue
-rwsr-xr-x 1 root root 143676 Jun 5 15:51 /usr/sbin/pppd
This is not an installer issue.
This defect is considered MUST-FIX for Winston Gold-release
Except for /etc/shadow (which I think would probably benefit from
being read-only for root), all of these permissions should match the
installed system as of linuxconf-1.19r1-7 and later (beta 4). Please
reopen this bug if you find this continues to be a problem.
You are correct. On beta4 everything cleared up except /etc/shadow.
So, I'd like to re-open this bug so that /etc/shadow can have the
proper permissions post-install. They should be 100400, not 100600.
Should the bugzilla category change?
Probably, but there are enough packages that modify that file to make
it hard to guess which one it's best filed against.
*** Bug 13617 has been marked as a duplicate of this bug. ***
this should be fixed in the final release.