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: <200308140116.h7E1GoRK012290@caligula.anu.edu.au>
From: avalon at caligula.anu.edu.au (Darren Reed)
Subject: DDoS on the 16th - Fail if no DNS resolution?

In some mail from Jason Witty, sie said:
> 
> All,
> 
> 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)?

Just to flip back to the 15th/16th thing, the significant thing here is
if it is using localtime vs GMT time then it will be the 16th in some
parts of the world before others...eg the West coast of USA is 7 hours
ahead of the East coast of Australia, but a day behind, so come 00:01
Saturday the 16th in Australia, it'll be 7:01am in Seattle on Friday the
15th...

Darren