full-disclosure - DDoS on the 16th - Fail if no DNS resolution?

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: <3F3AEF8C.5020300@ameritech.net>
From: dbailey27 at ameritech.net (northern snowfall)
Subject: DDoS on the 16th - Fail if no DNS resolution?

> Has anyone tested this worm yet to see what it'll do if you set up an 
> internal DNS entry for windowsupdate.com to point to a black hole 
> address (127.0.0.1 for example) and then set the system clock to be 
> August 16th (this Saturday)?

Has anyone taken the time to read the assembly to see if
the worm exits if it can't find an IP? Rather than point
windowsupdate.com to 127.1, just force your dns to return
lookup failure.

If the worm sees an error when it performs a URL lookup,
maybe it dies. It wouldn't have *anything* to DoS.

Don

http://www.7f.no-ip.com/~north_