Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: [Full-Disclosure] Verifying patches on MS servers |
|---|---|
| Date: | Mon, 29 Mar 2004 16:44:12 -0500 |
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@lists.netsys.com [mailto:full-disclosure-admin@lists.netsys.com] On Behalf Of Federated Information Security Sent: Monday, March 29, 2004 11:07 AM To: full-disclosure@lists.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@oxygen.com and destroy all electronic and paper copies of this e-mail.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Full-Disclosure] Re: Addressing Cisco Security Issues, Exibar |
|---|---|
| Next by Date: | [Full-Disclosure] RE: Addressing Cisco Security Issues, Lou Zirko |
| Previous by Thread: | [Full-Disclosure] Verifying patches on MS servers, Federated Information Security |
| Next by Thread: | [Full-Disclosure] RE: new internet explorer exploit (was new worm), Drew Copley |
| Indexes: | [Date] [Thread] [Top] [All Lists] |