Valhalla Legends Archive

Quote from: Grok on September 17, 2003, 08:30 PM
I still don't see it happening?  Still getting 404's when typing nonexistent .com and .net domains.

You shouldn't be getting a 404 for that at all - a 404 requires a response from the target server.  Nonexistant domains should result in a different error because the connection cannot be established (or even attempted).

Now this is a bit interesting.  VeriSign is claiming that "Both individual users and enterprises have been giving very positive feedback [about them hijacking unrecognized .com/.net domains]".  I guess they haven't heard that the BIND maintainers thought the problem was urgent enough to write and distribute an emergency patch to block SiteFinder.

Ugh ... it caught up with me and now I see the evil sitefinder.

http://slashdot.org/article.pl?sid=03/09/19/039214&mode=thread&tid=123&tid=126&tid=95&tid=99
They're getting sued over it.  The case looks like it's actually probably going to be a win, too.

Quote from: Soul Taker on September 19, 2003, 12:42 AM
http://slashdot.org/article.pl?sid=03/09/19/039214&mode=thread&tid=123&tid=126&tid=95&tid=99
They're getting sued over it.  The case looks like it's actually probably going to be a win, too.

Yup - IANAL, but they have a pretty compelling argument.

Quote from: Grok on September 17, 2003, 08:30 PM
I still don't see it happening?  Still getting 404's when typing nonexistent .com and .net domains.

You can't honestly be complaining about that... Verisign's pages are so ugly and plain it's not funny.

Did you mess with the 404 page or anything Grok?

ICANN needs to stop Verisign, damnit.

Quote from: Soul Taker on September 19, 2003, 12:42 AM
http://slashdot.org/article.pl?sid=03/09/19/039214&mode=thread&tid=123&tid=126&tid=95&tid=99
They're getting sued over it.  The case looks like it's actually probably going to be a win, too.

Use the url tag so we can click the link!

link

Never!

I have decided to finally post something of use to post...
Beat Verisign redirect!

It looks like ICANN is finally taking action against VeriSign.  However, as of 24 hours later, VeriSign has yet to comply.

Quote from: j0k3r on September 20, 2003, 06:36 AM
I have decided to finally post something of use to post...
Beat Verisign redirect!

Err.. I think that was one of the first things I said:

Quote from: iago on September 16, 2003, 07:13 PM
In my hosts file:
216.239.41.99 sitefinder.verisign.com

That way, at least I don't see their page :-)

Only instead of redirecting it to localhost, it would make more sense to direct it to 0.0.0.0 or, what I did, direct it to google.com

Looks like ICANN is finally taking real action against VeriSign.

ICANN is giving VeriSign until tommorow to undo the .com/.net wildcards, "or else" - it sounds like they're threatening to revoke VeriSign's contract.

Good. I can hardly believe that something this dumb was allowed to happen in the first place...

http://biz.yahoo.com/prnews/031003/sff057_1.html
"VeriSign Will Temporarily Suspend Web Navigation Service in Order to Continue To Work With Internet Community Towards a Long-Term Implementation"