full-disclosure - What to do with a "burned" dns record? (was: sco.com -> slow? :)

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]

From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: What to do with a "burned" dns record? (was: sco.com -> slow? :) 

On Mon, 02 Feb 2004 00:04:08 +0100, Benjamin Schweizer <besh@....net>  said:

> The big question is: what will happen to this "burned" domain name? It
> will need months till this packetstorm will calm. Is there a more
> professional idea than removing the a records?

Hmm.. "professional" and (implied) "SCO" in the same sentence.

Remember you're talking about a company that filed this in its 10K with
the SEC back on Jan 28:

"Additionally, we have recently experienced a distributed denial-of-service
attack as a result of the "Mydoom" worm virus. It is reported that the effects
of this virus will continue into February 2004."

Yep.  Jan 28 was the *filing* date.  Figure they actually *wrote* that
at least a day or three before.

So when did this DDoS actually start? ;)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040201/91a71499/attachment.bin