full-disclosure - Re: Microsoft Security, baby steps ?

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: <04F92BA33955D51195B700508B4AB6E9160A5BFC@dslak12.dnznet.co.nz>
From: StuartF at datacom.co.nz (Stuart Fox (DSL AK))
Subject: Re: Microsoft Security, baby steps ?

> 
> Come on Microsoft. How about putting together a single file 
> that contains all the "critical" security updates since the 
> last service pack for a given OS? 

How about every time they release a fix, they also release a rollup, so you
can either download the individual fix, or all the fixes up to that point?

> Who knows, perhaps then we'd get sensible 
> results out of MBSA?

Is it just me, or does the idea of having to have the Remote Registry
Service running to use the MBSA really annoy everyone else as well?

> 
> I use kickstart and the genhdlist package with Red Hat to 
> ensure that any installed system has all the updates 
> installed on the first boot after installation. Why then does 
> Windows have to lag so far behind?

A combination of SMS & SUS can provide almost the same thing, but having to
put SMS in isn't really desirable.

Cheers

Stu