full-disclosure - How to patch your systems (was Re: DCOM RPC exploit)

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: <200307281812.h6SICV5k004556@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: How to patch your systems (was Re: DCOM RPC exploit) 

On Mon, 28 Jul 2003 14:08:06 EDT, zorkshin@...pabay.rr.com said:
> If you use Active Directory, why not assign the patch package to all
> computers? Shouldn't this be quite easy ?

Yeah.. You assign the patch package, push it out - and find out that the
patch doesn't actually *make* it to all the machines because of the issue
identified in the KB article.  That's the *POINT*.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20030728/51fd3d12/attachment.bin