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 for Android: free password hash cracker in your pocket

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

Message-ID: <ELEOLHOJFMBPBFCJHOCIKEAJDPAA.aditya.deshmukh@online.gateway.technolabs.net>
From: aditya.deshmukh at online.gateway.technolabs.net (Aditya, ALD [Aditya Lalit Deshmukh])
Subject: Cronning Update Jobs

> off-list to tell me so. I'd hate for this to turn into another spammy 
> thread :p

hope all people would do the same thing .... 

>     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. 

'emerge sync && emerge -u world' is one hell of a good way of updating all the pakages but it might just overload the server or the bandwidth for your net connection ... 12 hours is very short interval i think, how about something like once every 5-6 days or once a week ? 

this way you are sufficiently current 

- just do chcek the log files manually every now and then to see if the cron job is actually working or not ;)

-aditya


________________________________________________________________________
Delivered using the Free Personal Edition of Mailtraq (www.mailtraq.com)