Bugzilla – Bug 138549
Permissions for cron.daily cron job too restrictive
Last modified: 2005-12-14 15:17:00 UTC
[sh @ snell] /etc/cron.daily 34 % ls -l total 44 -rwxr-xr-x 1 root root 393 Sep 9 18:11 logrotate -rwx------ 1 root root 948 Sep 13 01:58 suse-clean_catman -rwx------ 1 root root 1196 Sep 13 01:58 suse-do_mandb -rwxr-xr-x 1 root root 719 Sep 13 02:12 suse-tetex -rwxr-xr-x 1 root root 1875 Sep 1 2003 suse.de-backup-rc.config -rwxr-xr-x 1 root root 2059 Sep 8 2003 suse.de-backup-rpmdb -rwxr-xr-x 1 root root 566 Jul 23 2004 suse.de-check-battery -rwx------ 1 root root 1761 Sep 9 18:26 suse.de-clean-core -rwxr-xr-x 1 root root 1320 Jul 27 15:28 suse.de-clean-tmp -rwxr-xr-x 1 root root 371 Sep 1 2003 suse.de-cron-local -rwx------ 1 root root 1538 Sep 9 18:26 suse.de-updatedb [sh @ snell] /etc/cron.daily 35 % ls -l | grep '....---' -rwx------ 1 root root 948 Sep 13 01:58 suse-clean_catman -rwx------ 1 root root 1196 Sep 13 01:58 suse-do_mandb -rwx------ 1 root root 1761 Sep 9 18:26 suse.de-clean-core -rwx------ 1 root root 1538 Sep 9 18:26 suse.de-updatedb There is really no reason whatsoever to have permissions for those cron jobs that restrictive. They should all be 755. There is nothing secret in them. suse-clean_catman and suse.de-updatedb belong to package "man" -> werner@suse.de
Sorry, suse_clean_catman and suse-do_mandb of course, not suse.de-updatedb (separate bug report for that one follows).
Fixed