full-disclosure - Verifying patches on MS servers

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

Message-ID: <D89E9C009C6E5B4381DCBE89CA703CEE06438ACC@MI8NYCMAIL04.Mi8.com>
From: pwicks at oxygen.com (James Patterson Wicks)
Subject: Verifying patches on MS servers

We use HFNetChk Pro.  It really make patch management easy when you have
many servers.

http://www.shavlik.com/pHFNetChkPro.aspx

-----Original Message-----
From: full-disclosure-admin@...ts.netsys.com
[mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of Federated
Information Security
Sent: Monday, March 29, 2004 11:07 AM
To: full-disclosure@...ts.netsys.com
Subject: [Full-Disclosure] Verifying patches on MS servers

I've got a server that broke and had to be patched by uninstalling and
reinstalling a bunch of software, including various patches and maybe
even a service pack.  What's my best way to scan the server to make sure
no outdated .dlls were laid down or restored?  If I'm not mistaken, most
microsoft tools check the registry, which might not be accurate in this
case.  My options right now are ISS internet scanner, nessus, MBSA et
al, which is best?

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html

This e-mail is the property of Oxygen Media, LLC.  It is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this e-mail or the information contained herein by anyone other than the intended recipient is prohibited. If you have received this e-mail in error, please immediately notify us by sending an e-mail to postmaster@...gen.com and destroy all electronic and paper copies of this e-mail.