[lug] Why cron.allow and cron.deny?
Jeffrey S. Haemer
jeffrey.haemer at gmail.com
Mon Jan 13 11:24:19 MST 2014
That's sort of what cron originally
though as a daemon.
I don't know the history, but the v7 man page doesn't indicate that
Kernighan's cron (v7) had either. I could imagine that cron.allow and
cron.deny were initially stuck in not as security but as ways to manage the
Perhaps Dick Dunn or Dave Taenzer remembers. I'd ask Evi, but ....
On Mon, Jan 13, 2014 at 10:47 AM, Lee Woodworth <blug-mail at duboulder.com>wrote:
> On 01/13/2014 09:16 AM, Rob Nagler wrote:
>> I still don't get it. What's the difference between cron and this?
>> while true; do
>> sleep 60
>> Or, for the more abusive:
>> while true do
>> sleep 60
>> ssh some-target.com do_something
> A small difference: user scripts don't involve a privileged process
> and it's possible security holes.
>> 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
> 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
Jeffrey Haemer <jeffrey.haemer at gmail.com>
720-837-8908 [cell], http://seejeffrun.blogspot.com [blog],
*פרייהייט? דאס איז יאַנג דינען וואָרט.*
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the LUG