full-disclosure - MS should point windowsupdate.com to 127.0.0.1

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3F3C8DAA.7000301@dylanic.de>
From: security at dylanic.de (Michael Renzmann)
Subject: MS should point windowsupdate.com to 127.0.0.1

Hi.

Schmehl, Paul L wrote:
> Given that scenario, please apply your scintillating logic to the
> problem of patching this machine to protect it against threats that were
> discovered *after* SP2.

How about setting up a transparent firewall (that is, a Linux bridging 
box with firewall patches applied, so it is able to filter packages that 
travvel through the bridge). Another way would be setting up something 
like hogwash (iirc). This way one could react to every vulnerability by 
setting up correct filters / filter patterns.

Nevertheless I guess I had to live with one minus point, as I currently 
see no way to insert the box without any interruption of service. A 
(very short) interruption will occur, but as long as the machine relies 
on tcp it should handle the short networking outage.

Just my 0.02$

Bye, Mike