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: <20040328152401.GH1112@ngolde.de>
From: nion at gmx.net (Nico Golde)
Subject: Cronning Update Jobs

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
-- 
Nico Golde                | nico@...lde.de      | 310777820@ICQ | nion@....net
http://www.ngolde.de      | GnuPG Key: http://www.ngolde.de/gpg/nico_golde.gpg
Fingerprint               | FF46 E565 5CC1 E2E5 3F69  C739 1D87 E549 7364 7CFF 
vim -c   ":%s/^/WhfgTNabgureRIvzSUnpxreT-Tavba/|:%s/[R-T]/ /Ig|:normal ggVGg?"