full-disclosure - SQL Server patch - why doesn't Windows update help?

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

Message-ID: <200301301744.h0UHi5Hb062822@mailserver1.hushmail.com>
From: netw3_security at hushmail.com (Curt Wilson)
Subject: SQL Server patch - why doesn't Windows update help?

-----BEGIN PGP SIGNED MESSAGE-----

On Thu, 30 Jan 2003 07:30:05 -0800 Darren Reed <avalon@...mbs.anu.edu.au> wrote:
>I was just thinking to myself, hmmm, I have SQL Server something*
>installed on one of my Win2K boxes (service is turned off), I wonder
>if I have this patched as I do regular checkups with "Windows Update"...

Windows Update does not cover SQL Server. You need to use the Microsoft Baseline Security Analyzer if you are looking for an automated method in this case. MBSA handles a few things that WU does not, for instance SQL Server, and Exchange. Admins sometimes become complacent, thinking that "I run Windows Update and so now I'm secure". WU helps, but is only a piece of the Windows patching pie. MBSA is useful, although I've found that it misreports a variety of items, so you still have to vigilant.

-----BEGIN PGP SIGNATURE-----
Version: Hush 2.2 (Java)
Note: This signature can be verified at https://www.hushtools.com/verify

wmMEARECACMFAj45ZGIcHG5ldHczX3NlY3VyaXR5QGh1c2htYWlsLmNvbQAKCRBGd/Yw
aRH3K8l0AJ42vFGXbNf/UuJLTHMusaCGNILKoACfR6Rn2+ELkyHBxj3kTKNohOTkd60=
=4Oyu
-----END PGP SIGNATURE-----