Verisign Hijack > 127.0.0.1

127.0.0.1

I just "null routed" the sitefinder site...

# block nsi sitefinder

/sbin/ipchains -A output -p tcp -d 64.94.110.11/32 -i ppp0 -j DENY
/sbin/ipchains -A output -p udp -d 64.94.110.11/32 -i ppp0 -j DENY

Looks like the IP address is now 12.158.80.10
64.94.110.11 doesn't work for me anymore.

Load balancing perhaps?

They are hard at work making a patch for bind to ignore verisign injection their wildcard BS.

AP Article on yahoo news about it



Also, if you look at the source code (sitefinder.verisign.com), verisign has an image tag that is actually working as a 'web-bug' tracking you.

It is pointing to verisignwildcard.112.2O7.net.

I wonder if writing to their Sponsors from their new page would do any good?

I hope my isp blocks this bs, how can I verify a 'real' email address in my website forms anymore?

Spam? How to deal with it now? Rework everything because verisign decided to abuse dns? They should get their .com etc cert revoked and fined and jailed and.. Errrrrrrrrrrrrr.......
[text was edited by author 2003-09-16 19:35:29]

The federal government gave Network Solutions the authority
to manage the Internet's DNS infrastructure for the .com
and .net TLDs. Now that Verisign has abused that trust that
the Feds placed in them, they ought to revoke that
authority from Verisign, in addition to meting out fines
and jail time for their CEO and Board of Directors. I
think the fine ought to be at least a $1 billion.
--
"Kayura or Badamon, whichever you are, you should know that I will never give up this battle. By the will of the Ancient, I shall succeed!" - Shuten (Anubis) from the Ronin Warriors.

reply to Bobcat

said by Bobcat:

---

Looks like the IP address is now 12.158.80.10
64.94.110.11 doesn't work for me anymore.

---