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
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1821566
Title:
cron ignores whole crontab if one line has error
Status in cron package in Ubuntu:
Invalid
Bug description:
Ubuntu 18.04.
Let's create error entry in /etc/crontab:
00 09 * * 4 1 root /usr/local/bin/geoiprenew.sh
restart cron
systemctl restart cron
мар 25 10:29:02 ovpn1 cron[12403]: Error: bad username; while reading
/etc/crontab
мар 25 10:29:02 ovpn1 cron[12403]: (*system*) ERROR (Syntax error, this
crontab file will be ignored)
Expected behavoir is only line with error is ignired.
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1821566/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
