IMHO, this would be bad. The Cron Daemon would have to sanitize the
input of the crontab each time it checks the file for running
(presumably every minute, unless their is a way of notifying the cron
daemon of a new crontab.)
The default crontab in debian creates a file in /tmp, the user modifies
it using their favorite editor, saves it, crontab then performs a sanity
check on it. If all is good it copies the file into the crontab
directory and notifies the daemon of the new crontab.
I think the current system works well...
let's combine it :)
user puts his crontab in his home...
launches something non-suid that notifies the cron deamon that there's a
new entry, cron sanitizes it and copies to its directory...
this would allow crontab to run non-suid since it would just have to be
notified of changes, and it could run as a deamon...
greetings,
Kuba BIGHard Jakubik
