[lug] Why cron.allow and cron.deny?

Quentin Hartman qhartman at gmail.com
Mon Jan 13 08:53:35 MST 2014

It's a possible abuse/attack/oops vector. If someone sets up a expensive
process to happen every minute, they could effectively DOS your server.

It's generally a concern only public-access, or quasi-public access systems


On Mon, Jan 13, 2014 at 8:45 AM, Rob Nagler <nagler at bivio.biz> wrote:

> Why would one want to prevent an ordinary user from using cron (or at)?
> Thanks,
> Rob
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20140113/95e03acd/attachment.html>

More information about the LUG mailing list