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
| ||
|
Message-ID: <Pine.GSO.4.53.0308142351560.3375@nova.ee.ethz.ch> From: oetiker at ee.ethz.ch (Tobias Oetiker) Subject: MS should point windowsupdate.com to 127.0.0.1 Folks, How about MS standing up for the mess, and changing their own DNS to point all request for windowsupdate.com and whatnot to 127.0.01 ? This will null the effect of the syn flood very effectively. Only proxies will be affected. As far as I see it, they will not be able to use these names productively for the foreseeable future anyways ... So they will have to issue an update for windows-updater thourgh other channels (like their homepage for example) to point it to a different web-site .. that should not be all that much of a problem. If MS does NOT make this change to their DNS, I can see many routers who are trying to track connections toppling over in interesting ways. Because the local techs have no clue, it will take the affected companies ages to get back on the net. tobi -- ______ __ _ /_ __/_ / / (_) Oetiker @ ISG.EE, ETZ J97, ETH, CH-8092 Zurich / // _ \/ _ \/ / System Manager, Time Lord, Coder, Designer, Coach /_/ \.__/_.__/_/ http://people.ee.ethz.ch/~oetiker +41(0)1-632-5286
Powered by blists - more mailing lists