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

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

From: kain at kain.org (Bryon Roche)
Subject: How to patch your systems (was Re: DCOM RPC exploit)

On Mon, Jul 28, 2003 at 02:12:31PM -0400, Valdis.Kletnieks@...edu wrote:
> 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*.

Please excuse the nt4-ism, but:
execution from netlogon script to install patch, force reboot on host to load patch?


-- 
Bryon Roche
Professional {Developer,Linux/MS Consulting,Software Architect}
<kain@...n.org>
PGP Key Fingerprint: FE0D EC23 6464 726A CD54  48D3 04AD 86FE 6878 ABD5
Fortuna est caeca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20030728/6c81be54/attachment.bin