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]

Message-ID: <EKECJMGPAACGOMIGLJJDGEJPEBAA.geoincidents@getinfo.org>
From: geoincidents at getinfo.org (Geo.)
Subject: Re: Microsoft Security, baby steps ?

>>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?<<

It doesn't address the issue. The requirement is that some MS customers need
to patch without putting the machine on the internet. For whatever reasons.

Is that such an unreasonable request?

Geo.