full-disclosure - Verisign abusing .COM/.NET monopoly, BIND releases new

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: anub-full.disclosure.200309 at open.mine.nu (Christopher Kruslicky)
Subject: Verisign abusing .COM/.NET monopoly, BIND releases new

On Wednesday 17 September 2003 03:13, Michael Renzmann wrote:

> Yeah, seams like that. For example, the (I think) non-existant
> dulladulladulla.net resolves to 64.94.110.11, as well as
> bollabollabolla.net or verisignsucks.net. So blocking any DNS reply
> containing this IP could be a way to prevent that Verisign "commercial
> break".


And just to make the whole thing a little funnier, they've decided not to 
resolve verisignsucks.com anymore =)

$ host verisignsucks.com
Host verisignsucks.com not found: 2(SERVFAIL)

$ host verisignsucksdonkeyballs.com
verisignsucksdonkeyballs.com has address 64.94.110.11