bin/43623: /etc/crontab dosen't processed any more

[taca%back-street.net@localhost]

>Number:         43623
>Category:       bin
>Synopsis:       /etc/crontab dosen't processed any more
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 15 14:00:00 +0000 2010
>Originator:     Takahiro Kambe
>Release:        NetBSD 5.99.36
>Organization:
Takahiro Kambe
>Environment:
        
        
System: NetBSD edge.back-street.net 5.99.36 NetBSD 5.99.36 (VMWARE-F3-MONO) 
#19: Wed Jul 14 15:51:02 JST 2010 
taca%edge.back-street.net@localhost:/var/obj/sys/arch/i386/compile/VMWARE-F3-MONO
 i386
Architecture: i386
Machine: i386
>Description:
        /etc/crontab dosen't processed current cron(8) any more.

>How-To-Repeat:
        There was errors in /var/log/cron.

2010-07-15T09:36:22.896356+09:00 edge.back-street.net cron 1013 - - (*system*) 
BAD FILE MODE (/etc/crontab)

>Fix:
        It seems that current cron(8) think /etc/crontab as each user's crontab.
        in src/external/bsd/cron/dist/database.c:

        if ((statbuf->st_mode & 07777) != 0600) {
                log_it(fname, getpid(), "BAD FILE MODE", tabname);
                goto next_crontab;
        }

        So, "chmod 600 /etc/crontab" could be workaround.  But there should be
        something to distinct the system crontab and user's crontabs.

>Unformatted: