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

From: Simon.Richter at hogyros.de (Simon Richter)
Subject: Re: Microsoft Security, baby steps ?

Hi,

> When you want to be the leader, you don't ask questions like that. You
> recognize problems and you solve them and one of the problems today for
> Windows is that MS is making it very difficult to keep patched if the user
> doesn't want to put the machine on the net BEFORE it's fully patched. (a
> valid security oriented attitude)

Hrm, how about inventing an option (at install time) that places a very
restrictive firewall on the network connection by default, say, only
outgoing port 80 to windowsupdate.com (or even better, only let it
establish a secure tunnel there), so you can patch and then loosen the
firewall settings after that?

Granted, you won't be able to install AntiSpy or sth. like that from
the 'net, then, but the < $1 for a CD-R shouldn't really matter if you
have just bought Windows.

   Simon

-- 
GPG Fingerprint: 040E B5F7 84F1 4FBC CEAD  ADC6 18A0 CC8D 5706 A4B4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040317/a89f8181/attachment.bin