full-disclosure - [despammed] RE: Automating patch deployment

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>] [day] [month] [year] [list]

From: LevinsonK at STARS-SMI.com (Levinson, Karl)
Subject: [despammed] RE: Automating patch deployment

I've heard this argument many times, and for me it holds no water.  You need
to test your patches no matter how you push them out, period.  Testing
patches and automating patch installation are two different issues and are
*not* mutually exclusive.  The real question is, would you rather have an
easier way to push out updates so that your staff has more time to test
patches thoroughly?  

> ----- Original Message ----- 
> From: Johnson, Mark 
> To: George Peek ; full-disclosure@...ts.netsys.com 
> Sent: Wednesday, August 06, 2003 7:12 AM
> Subject: RE: [Full-Disclosure] Automating patch deployment

Automation of update patches? Not on your Nellie! I would have a machine
download patches and try installs on it before I felt comfortable about
passing them on to others.