Common cron implementations have one simple security hole: they make it easy
to exploit the cron jobs because they are predictable. Here is the solution:
a cron version that starts the jobs _on average_ hourly, daily, weekly or
monthly, but keeps the actual run times unpredictable.
Additionally, this version of cron creates less load peaks than traditional
implementation, both on the box running it and on update servers when using
cron-scheduled update scripts.
Sound interesting? Check it out on alt.sources: <privacy.net>
Feel free to post some comments....