full-disclosure - [normal] RE: Windows Dcom Worm planned DDoS

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: <Law11-OE59n6Mnv3Ap40001e0ff@hotmail.com>
From: se_cur_ity at hotmail.com (morning_wood)
Subject: [normal] RE: Windows Dcom Worm planned DDoS

i kinda agree that simple http redirection works best here
windowsupdate.com -------> wescrewedup.microsoft.com
as the attacking agent is not http, and http is what is needed, hell you
could also
only allow port 80 tcp/ip requests on the filters as well. Dropping
everything else
at the border.
going 127.0.0.1 for a day or two is also an idea
or not

morning_wood