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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Subject: Verisign abusing .COM/.NET monopoly, BIND releases new

> > Is it always returning the same IP address, 
> 
> 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".
> 
> Did anyone else notice that the host behind this IP seems to 
> be down? No 

http went up and down several times yesterday. One moment it works, the
other not (and vice versa). I think they have underestimated the number
of typos and as such under-powered the machine. A good indication is the
single IP (even though that eventually is a reverse proxy).

Anyhow, I wouldn't count that this will be the only IP they use. Just
imagine they move this over to akamai...

As they behave like the spamers, I think they will also use their
methods to make safeguards fail. IMHO only big media & gouvernment
attention as well as harsh words from the internet bodies could help.
But Verisign seems to be so resistant against any ethical business.
Maybe it would help if anyone of use would actually call them once a day
to tell them that they should stop this. No, not mail. Calling, in the
sense of a call center DoS ;) I think this is ethical as they are
causing big troubles to us, so we can complain...

Rainer