Well, this design is wrong then, because I'm talking about /etc/crontab ,not
about /etc/cron.d directory. System crontab ( /etc/crontab ) is protected by
access rights, so it can't be changed by malicious user.
And any error causes cron almost stop working, because in my case
/etc/crontab
I'm afraid that this is by design, to prevent a malicious user from
dumping basically anything into one of the crontab directories.
An attacker once compromised a debian.org host by triggering a crafted
core dump in one of the crontab directories, and the daemon kept trying
to execute lines until
2 matches
Mail list logo
