full-disclosure - Cronning Update Jobs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <40673F9C.2080009@elvandar.org>
From: remko at elvandar.org (Remko Lodder)
Subject: Cronning Update Jobs

Hi nico,


Nico Golde wrote:
> Hallo Luke,
> 
> * Luke Norman <luke@...manonline.co.uk> [2004-03-27 17:28]:
> [...] 
> 
>>My question is this - are there any security risks to adding this 
>>command to a cron job, and having it execute say, once every 12 hours. 
>>Any and all input appreciated
> 
> 
> is it a risk if you do it manually? see? ;-)
> regards nico
=> at least with a manual run you can see what happends, an automated 
update goes without visual see-ing of what happends... So in that way 
automated updates are a bigger risk in security then manual runs.

HTH,

Kind regards,

Remko Lodder
Elvandar.org/DSINet.org
www.mostly-harmless.nl A Dutch community for helping newcomers on the 
hackerscene