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 it hit a valid one.
** Changed in: cron (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821566
Title:
cron ignores whole crontab if one line has error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1821566/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
