Slashdot Mirror


3rd Lawsuit Against VeriSign Seeks Class Action

dmehus writes "A third lawsuit has been filed late Friday in a federal district court in California against VeriSign, Inc. over its controversial DNS wildcard redirection service known as SiteFinder. According to the article, it was filed by longtime Internet litigator Ira Rothken. In addition, while two other lawsuits have been filed by Go Daddy Software, Inc. and Popular Enterprises, LLC. in Arizona and Florida, this is the first lawsuit to seek class-action status."

128 comments

  1. No Shame by Anonymous Coward · · Score: 5, Insightful

    Verisign truly has no shame, but the reason they can get away with this is simple: most people on the net now are new to it, and have not the faintest idea about how the net used to be a cooperative medium, where bullshit like this was not tolerated. Today? No such luck, users expect to be scammed and abused with every click, they will accept this, and they are the majority.

    1. Re:No Shame by Jameth · · Score: 1

      Actually, it doesn't seem like it is being tolerated. That's three major lawsuits in about two weeks, as well as a pretty strong message from ICANN about it, as well as a couple other people and organizations. Not doesn't seem like 'tolerance' to me

    2. Re:No Shame by BiggerIsBetter · · Score: 1

      true, except they don't even reaslise they are being scammed. paying for everything you do, and being constantly subjected to advertising the the norm for most people. they don't know any different and accept it as being normal online.

      unfortunately, the large corps that 0wn the net now are loving it too. most punters think the internet is msn and explorer, and that miscrosoft runs the internet. unless they use aol. it's just bits and packets to me, but to them it's "an experience". or something.

      the only people who think it should be any different are us old-timers (over 25?) who haven't sold out, so i think it's fair to say the internet as we knew it is dead, or at least well underground (pun intended).

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
    3. Re:No Shame by LostCluster · · Score: 1

      The Internet was founded as an academic and research universe, then it went commercial...

    4. Re:No Shame by littlerubberfeet · · Score: 1

      Sure, the ICANN has sent their message, and lawsuits exist, but it is being tolerated. How many common internet users know what w3c is? Or the ICANN? How many people know the difference between AOL and the internet. The fact is that most people could care less about being screwed over, As this AC pointed out. 50 million people signed a do not call list. They expect the internet to be annoying and full of popups. If 50 million people signed a petition to censure Verisign, you bet there will be some legislation. Regular folks just don't care.

      --
      Sig (appended to the end of comments you post, 120 chars)
    5. Re:No Shame by Jameth · · Score: 1

      50 million people signed a do-not-call list because it is possible to enforce and because the problem has been around for years. This is a really NEW problem, and it's getting plenty of attention. It is only a problem for regular internet users if these current measures fail.

      You can't expect an issue to be a problem to people so quickly. If I did not read Slashdot, I wouldn't care about this. Why? The last time I mistyped an address was longer ago than I can remember. After all, I'm a decent typist and usually follow links. This is being dealt with by the organizations and individuals for whom it is a problem.

  2. I for one... by rekkanoryo · · Score: 2, Informative

    will be happy to see VeriSign blasted on this one. This is one of the stupidest ideas I've ever seen, and is a pain in the ass. I also wouldn't mind seeing someone else have control over the TLDs VeriSign currently controls.

    1. Re:I for one... by Anonymous Coward · · Score: 0

      am glad that your post did not include the word overlord.

  3. What's the big deal? by Anonymous Coward · · Score: 5, Insightful

    Recently, the .museum TLD went live. It's just like any other TLD except that domains that don't exist diect you to a page saying the domain doesn't exist and with a couple of links. Many other countries also do this sort of thing with their domains. They're not very different than Verisign's SIteFinder, but there's little to no outcry over this. I'm curious because a lot of the objections about SiteFinder should also be true about the .museum TLD and all the others. What's different here?

    And don't tell me because nobody uses those domains, that it's okay. That's just an elitist view and also blatant hypocrisy.

    1. Re:What's the big deal? by rekkanoryo · · Score: 2, Insightful

      I would bet it's because most people here don't realize that's happening. If the TLD was more common, more people here would know it's happening and bitch and whine and moan just like we're doing over VeriSign SiteFinder.

    2. Re:What's the big deal? by doktor-hladnjak · · Score: 3, Interesting
      What's different here?

      The big difference as I see it can be broken down to 2 big points:

      1. Verisign is NOT the only company through which you can register a com or net domain. Many of these other smaller domains (small islands in the south Pacific, .museum, etc) usually have one government sanctioned registrar. Leading to the registration site in those cases is in many cases helpful. Although there are no links to their registration forms, what's to stop them from doing that later?

      2. Verisign is running a search engine on SiteFinder, which they control. I don't believe they do it now, but they could very easily commercialize this search engine: ads, charging for high results in the search.

      3. com and net are much larger than other obscure domains that have already done this. Just because other TLDs have done it does not make it right! There are apparently some standards laid down by ICANN that have been broken by doing this.

      Bottom line though: just because they manage the TLDs, does not give them the right to break things for their own commercial gain.

    3. Re:What's the big deal? by Jameth · · Score: 2, Insightful

      Actually, its neither elitist nor hipocrisy. The .museum domain is for museums. Their page points you to a list of museums and an information page about the museum pages. VeriSign points you at adds, while they are running .net and .com, which have almost anything on earth hosted on them.

      The difference? The museum redirect is useful, the VeriSign redirect is useless and profiteering.

    4. Re:What's the big deal? by Anonymous Coward · · Score: 0

      Bullshit.

    5. Re:What's the big deal? by secolactico · · Score: 1

      I don't think it is different. Even if it's useful, it still can wrongly give false info.

      One of the complaints is that Verisign broke the way some anti-spam filters determine if the mail comes from a valid domain.

      Could this mean that spammers could use "jkfjjd.museum" and bypass this kind of filters?

      (Man, I hope someone else thought of this first for I'd hate to be the one that gave them this idea)

      --
      No sig
    6. Re:What's the big deal? by Paradoks · · Score: 1

      My issue with Verisign's SiteFinder is functionality; back when Internet Explorer started searching the net for the mistyped domain name, I quickly turned it off because I wanted to be able to fix my mistype in the address bar, and Internet Explorer's/MSN's search screwed it up. Verisign's search does the same, and you can't turn it off, or switch browsers. .museum gives you an informative page and still allows you to correct your mistake in the address bar.

      This is another one of those "features" that I'd prefer to avoid having foisted on me.

    7. Re:What's the big deal? by sa3 · · Score: 1

      Interesting index.museum doesn't exist except as a *.museum record, which I found out when I blocked wildcard records on that domain :|

    8. Re:What's the big deal? by LostCluster · · Score: 1

      2. Verisign is running a search engine on SiteFinder, which they control. I don't believe they do it now, but they could very easily commercialize this search engine: ads, charging for high results in the search.

      SiteFinder is already commericalized. Gambling isn't one of the most popularly looked for areas on the Internet, but it is one of the highest paying for redirections. The search engine also features Overture-like (if not powered by Overture already) paid placements...

      SiteFinder isn't being done out of kindness, it's a search for dollars...

    9. Re:What's the big deal? by r7 · · Score: 1

      >Recently, the .museum TLD went live. It's just like
      >any other TLD except that domains that don't exist
      >diect you to a page saying the domain doesn't exist
      >... What's different here?

      The difference, in a nutshell, is that this wildcard was
      only implemented after discussion by, and agreement
      from, the subdomains under .museum.

      r7

    10. Re:What's the big deal? by joe_plastic · · Score: 1

      No it was discussed earlier on slashdot even.
      Basicly I think it is not too much of a problem. You can even speed up the check by not even doing a look up on those domains and just scoring the same as if it were a nonexistant domain name.
      You probly would actually do it as a whitelist of conforming domain systems.

    11. Re:What's the big deal? by Anonymous Coward · · Score: 0

      The standard states that a missing page should return a 404-error code. There is a reason for this, (like making sure an address really exists). Verisign replaces this by a 302 (temporarily moved) code, screwing up the whole mechanics behind missing pages. An error is now a temporary problem. Some application might just start looping and trying the page again every hour! (Stupid example but you get the idea.)

      Other countries that re-direct to a "you can buy this site" page, still returns a 404 error, in line with the standard.

      In addition Versigne show (or will do so soon) ads to redirect you to places for them to make money (a % on every sales originating from them for example).

      Their contract is to take care of the system for the public at large, in respect of the standard, if they wanted to show adds they should have put it in the submission, and ICANN would have gave it to another business to do it properly. You cannot change (this service) provider like for your cable compa... oh wait! Like your long distance provider.

      Where does it stop anyway? Next it will be banners then popup?

      Imagine that each time you phone a friend, if you entered a wrong un-existing number, your phone company re-directs your call to some telemarketer? (The highest bidder). Oh crap! I hope they wont read this!

      This is just unacceptable, if they keep it up, ICANN will give the business to another party (what are the term of they deal anyway?)

    12. Re:What's the big deal? by Sphere1952 · · Score: 1

      I bet any other TLDs started up with an agreement that they could do it. VeriSign has no such agreement, and it would be unthinkable to allow such an agreement in the case of the .com and .net domains.

      Basically, VeriSign is making a power grab. The only appropriate response to such a power grab is to kill the company making the grab. It's time to bankrupt VeriSign.

      --
      Big Brother Bush is doubleplus ungood.
    13. Re:What's the big deal? by Anonymous Coward · · Score: 0

      And *.com and *.net have been around for MANY years, and it's a sudden turning-on of this 'feature'.
      If it's a new TLD, and the 'feature' is there from the start, that's different..

    14. Re:What's the big deal? by Anonymous Coward · · Score: 0

      "And don't tell me because nobody uses those domains, that it's okay. That's just an elitist view and also blatant hypocrisy."

      You saying it doesn't make it so, asshat. Talk about elitism. Sheesh.

    15. Re:What's the big deal? by Anonymous Coward · · Score: 0

      Oh, I don't know. Maybe its the fact that the unilateral change broke mail filters, rendered thousands of custom scripts useless, and forced organizations to change the configurations of thier web monitoring software just so Verisign could make a couple of bucks. And don't even get me started on non-http dns resolution headaches.

    16. Re:What's the big deal? by kawika · · Score: 1

      The big deal is that it's at the wrong conceptual level. The domain lookup for a non-existent domain should return "domain not found" and not refer the user to an IP that does not represent that domain. (I believe that could be called "misrepresentation".)

      A similar mistake is made by sites that do not return 404 errors when a page is not found on the site, but instead return 200 and some sort of "was this what you were looking for?" page. Instead I would prefer a 404 page with that content.

      Unfortunately, IE is broken and will display that worthless and uninformative "page cannot be displayed" message on a 404 unless the content returned is larger than 1024 bytes. To add insult to injury, IE refers to this as "friendly error messages"!

    17. Re:What's the big deal? by Nerd4News · · Score: 1

      "Could this mean that spammers could use "jkfjjd.museum" and bypass this kind of filters?"

      "(Man, I hope someone else thought of this first for I'd hate to be the one that gave them this idea)"

      Nope, the spammers already thought of it. Many ISPs have implemented spam filters that check the validity of a domain before allowing it through the server. This effectivly makes that check useless. Now, there are ways around this but considering how long it took my ISP to implement domain verification, I don't hold much hope for them fixing it anytime soon. Noticed a huge increase in SPAM lately? I have. Went from a few per week to hundreds. Thank Verisign.

      This is similar (but much worse) to typing "google" or "slashdot" into the address bar of IE or Netscape and being redirected to the MS or NS search page instead of where you really wanted to go. It's all about page views and eyeballs. And yes, I know this can be fixed in IE & NS but it doesn't come that way by default and relatively few know it can be fixed or how to do it. Thank God for Opera. It does it right right out of the box.

      Verisign has become the latest scum of the internet and should be banished from having any control over TLDs. It should have happened two years ago when they first tried to hijack domain registrations.

  4. Here's a question... by dnaboy · · Score: 5, Interesting

    Can one get in trouble for launching a DOS attack on an unassigned web address? Do they all by default belong to Veri$ign (OK, I couldn't resist porting the obligitory $, generally reserved for M$), or are they fair game to hit with reckless abandon?

    1. Re:Here's a question... by Anonymous Coward · · Score: 0

      How are you about to do a DOS attack on an unassigned IP address?

    2. Re:Here's a question... by Anonymous Coward · · Score: 1, Funny

      Guess they should have done this earlier, before the DOS against the non-existant windowsupdate.com was launched.

    3. Re:Here's a question... by Angram · · Score: 1

      Considering that your intent is to down VeriSign, it's irrelevant what combination of numbers you technically "attack".

      --

      GL
    4. Re:Here's a question... by dnaboy · · Score: 1

      I was more thinking have it hit [Insert Random Characters].com. It seems like it would be much harder to put the breaks on than an attack to a particular IP address, though, I must confess I'm not an internet security expert by any stretch of the imagination.

    5. Re:Here's a question... by Anime_Fan · · Score: 1

      root@kami / # alias slashdotted="DDOS -t death"
      root@kami / # host ifyousendmeadnsreplyyouagreethatthereplieddnswillb eslashdotted.com
      ifyousendmeadnsreplyyouagreethat thereplieddnswillb eslashdotted.com has address 64.94.110.11
      root@kami / #

      Special thanks to slashcode for inserting extra spaces for the site

    6. Re:Here's a question... by 1000101 · · Score: 1

      y0u h4v3 n0 ski11s s0 d0n'7 3v3n w0rry 4b0u7 i7. y0u c0u1n'7 h4X 4 br0wn p4p0r b4g. i ru13!

      WOOT

      j/k

    7. Re:Here's a question... by Anonymous Coward · · Score: 0

      No my intent was to test my firewall / httpd, I just mipselt the domain. It would have been obvious I mispetl it had verisign not co-opted non existant domains.

    8. Re:Here's a question... by lildogie · · Score: 1

      AHEM, the DOS attack you envision would be an attack on DNS, and would threaten DNS service for everyone.

      Unassigned DNS names don't have unassigned addresses.

      If you attack SiteFinder, you'll find that they have an owner, one who can afford expensive owners.

    9. Re:Here's a question... by Volmarias · · Score: 1

      Considering all of the traffic they expect, I doubt that anything less than a thousand 1337 h4x0rz performing a DDoS with a thousand machines for each of them would even make a dent. Besides, all those packets will just end up clogging the internet, making it slower for everyone.

    10. Re:Here's a question... by Anonymous Coward · · Score: 0
      y0u h4v3 n0 ski11s s0 d0n'7 3v3n w0rry 4b0u7 i7. y0u c0u1n'7 h4X 4 br0wn p4p0r b4g. i ru13!

      WOOT

      j/k


      Considering he's talking about a denial of service attack and didn't mention hacking any site, perhaps it's you own skills which are lacking?
    11. Re:Here's a question... by Anonymous Coward · · Score: 0

      Why do you use the term "DOS attacks"? Never initiate a DOS attack against anyone. On the Internet, it's very important to do unto others what you would have them do unto you.

      So, it's perfectly reasonable to embed something like <img src="http://www.zdsasdkfbsdkjfbaskdj.com/" width=1 height=1> in all of your web pages. Better yet, use a CGI that generates changing URLs. (I have done this on my web pages).

      The only situation where that would cause a surfer's web browser to attempt to connect to an actual host would be if someone was intercepting the lookup for the nonexistant domain and falsifying information. If that causes undue burden on anyone's servers, all they would have to do is stop proactively intercepting the lookups and requesting the connections.

      It's also perfectly legit to add Verisign whois server lookups to your widely distributed applications that would normally use DNS to determine whether a domain name is invalid and can no longer do so.

      I asked Verisign how to solve the broken DNS problem that they created, and they told me:

      "Utilities that currently use the DNS to determine if a domain exists can use VeriSign's Whois server to accurately determine if a domain exists."

      So determine away, but remember, do unto others as you would have them do unto you. If you were responsible for breaking DNS lookups, and you were willing to run a whois server to provide everyone on the Internet with a workaround, then double check every DNS lookup you make with a whois lookup.

  5. Re:Huh? by marcelC · · Score: 1

    CowboyNeal is the "I don't know what to choose" option of he old polls, when he world was flat, the air was clean and dogs were still barking out of their arses.

  6. Sitefinder gives ideas about BIND enhancement by Tirel · · Score: 1, Troll

    instead of the verisign sitelooker page, I suggest that BIND (the software that runs 60% of the DNS) should be enhanced in several ways: The most important one, IMHO, is to compute a list of close matches and present these choices to the user. They may use the Soundex algorithm or some other tricks to see if characters are transposed, if one characters is wrong, if one is missing, etc.

    If well implemented, this would solve 60% of the problem. The remaining 40% is due to the fact that people sometimes doesn't actually mistype a known address... they type a dead wrong address, such as "amazonbookstore.com" instead of "amazon.com". In this case, BIND should split up the phrase into separate word (in this case "amazon book store" and redirect to a search engine with those words as parameters. The big question in this case is: which search engine?

    I think that one should be able to choose, in one way or another. If not, Google would be my choice ;-)

    1. Re:Sitefinder gives ideas about BIND enhancement by Gwala · · Score: 1

      Thats a good idea, however its fundementally flawed for one part - it couldnt be done by BIND alone, BIND only does the name translation, it couldnt send to a search engine ...

      -Gwala

      --
      #!/bin/csh cat $0
    2. Re:Sitefinder gives ideas about BIND enhancement by DavidpFitz · · Score: 4, Insightful

      What about Email, IRC, USENET etc etc... How would that be forwarded to a search engine? HOw do I prompt a user in IRC to choose which is the mistyped addresses they really meant? Do you expect half the software for internet communication to be re-written?

      The Internet is not just the web!

      And this is a very stupid, ill-thought out idea!!

      D.

    3. Re:Sitefinder gives ideas about BIND enhancement by Tirel · · Score: 0, Troll

      The obvious solution to this would be for BIND to redirect non-existant queries to a search engine IP which would figure out your mistyped domain via referer. This, of coruse, brings up the question of referer-removing proxies, like privoxy. Now, I don't want to flamebait here, but who in the world uses those? Only criminals I would think. Why would a good netizen want to use such a tool which is obviously there to provide an extra layer of privacy on the internet (I use the term privacy lightly, since given enough focus, it's trivial to track people online). Privoxy is used 80% by people who distribute child pornography and 20% by paranoid linux hippies who like to exploit hard-working site-managers into oblivion by not viewing ads. I suggest that such proxies be made illegal and users of it expelled from the internet until they grow up or the police have enough evidence of their child molestation acts.

    4. Re:Sitefinder gives ideas about BIND enhancement by jhunsake · · Score: 1

      At first I thought you were just stupid. Now I realize you are a troll.

    5. Re:Sitefinder gives ideas about BIND enhancement by segmond · · Score: 2, Insightful

      and how often will bind work? DNS servers cache site, so there is moon.com and noon.com, noon.com falls off for a day or something and now all noon.com requests go to moon.com, noon.com comes back online, how long will the noon.com requests keep going to moon.com? HRM, cnn.com is popular, some crazy haxors get cnnn.com, and DDOS cnn.com and everything on its network out of this world, requests for cnn.com now start going to cnnn.com.

      I don't think the solution should be in bind. If I do a telnet host123 to see if it exists, I don't want to connect to host231 cuz bind thought that's what i wanted.

      --
      ------ Curiosity killed the cat. {satisfaction brought it back | it didn't die ignorant | lack of it is killing mankind
    6. Re:Sitefinder gives ideas about BIND enhancement by axxackall · · Score: 1
      I know what to do in a case of email:

      MTA must return (bounce) the message with the original error message (MX) not found) as well as all those rule/soundex-based search results. The sender then makes a correction based on newly available information.

      In order to protect mail-list agents, the addition field can be used, like "X-Bounce: NO" to switch-off the bouncing (by MTA) for such senders.

      As for IRC, when you connect to IRC your IRC program has a dialog, where more DNS disagnostics (including the suggested ine with search engine) can be inserted.

      --

      Less is more !
    7. Re:Sitefinder gives ideas about BIND enhancement by segmond · · Score: 1

      nah, it's not a good idea.

      % ping www.cnnn.com
      PING www.cnn.com (127.0.0.1): 56 data bytes
      64 bytes from 127.0.0.1: icmp_seq=0 ttl=240 time=5.6ms
      64 bytes from 127.0.0.1: icmp_seq=1 ttl=240 time=5.6ms
      64 bytes from 127.0.0.1: icmp_seq=2 ttl=240 time=5.6ms

      If I ping www.cnnn.com, I want to get the appropriate ping response.

      --
      ------ Curiosity killed the cat. {satisfaction brought it back | it didn't die ignorant | lack of it is killing mankind
    8. Re:Sitefinder gives ideas about BIND enhancement by KrispyKringle · · Score: 2, Informative
      Yeah, thats a pretty poor idea. See, first off, I think you are wrong about what the Soundex algorithm does. It categorizes names by similar phenomes, not by similar spelling. So it would recommend, say, yeehaw.com (is there one) as a replacement for yahooo.com, when obviously that should be yahoo.com.

      Second, and far more important, you forget that DNS is used for more than just web browsing. As someone pointed out above, what about protocols that do not support that search page? How do you present a search page to IRC users? Sure, you could just redirect them, but then you'd have all sorts of mistaken redirections. It would suck.

      Far better to leave it to the surfer's choice. As is, many browsers redirect to a search page if the host-name lookup fails. Thats the best method; it avoids issues with other protocols, with DNS caching of false replacements, or any of the other issues, while giving the surfer's browser full control over how to implement it, what search engine to use, etc. There is no real loss by leaving it to the browser, but many gains. Think. Then speak.

      Mensa member, eh? Beware of arrogance and stupidity.

    9. Re:Sitefinder gives ideas about BIND enhancement by GeorgeK · · Score: 3, Insightful

      This would ruin the authoritative nature of DNS. It's not supposed to be an "approximation" system. Doing the above would cause more problems than it would solve, as it would leave to misdirected emails, misdirected websurfers, and big privacy and security issues.

      Failed lookups are a good thing. It empowers the end-user to decide how to best handle those errors. Shifting that power to the registry (in the case of Verisign's Sitefinder), or to BIND (hosted by the ISP) would remove power from end-users.

    10. Re:Sitefinder gives ideas about BIND enhancement by KrispyKringle · · Score: 0, Troll
      Incidentally, Tirel, your signature really gives away your identity. Can't we just call you Krapongor?

      I mean, seriously. Did your dad beat you, or your mom not tell you she loved you? What sort of emotional issues would lead you to get such satisfaction from acting like an immature 13 year old on the Internet? Or are you a 13 year old (if so, trust me, you'll feel stupid about this when you're older)?

    11. Re:Sitefinder gives ideas about BIND enhancement by dark-nl · · Score: 1

      I don't see why it would have to be just one or the other.

    12. Re:Sitefinder gives ideas about BIND enhancement by daffmeister · · Score: 1

      And how, Mensa Member with your impressively high IQ, do you propose that bind, a piece of software that does not directly interact with the user, present this list of choices?

      Do you suggest it does this also for all other internet applications? (there is more than just the web you know).

    13. Re:Sitefinder gives ideas about BIND enhancement by Vengeful+weenie · · Score: 1

      I've said it before, and I'll say it again.

    14. Re:Sitefinder gives ideas about BIND enhancement by pod · · Score: 1

      DNS is not a search engine. DNS look ups are final, authoritative and precise. The host and/or record type you're looking for either exists, or it doesn't. You want a search engine, go to Google. Maybe Google will come up with a DNS search widget? But this functionality does NOT belong in DNS.

      --
      "Hot lesbian witches! It's fucking genius!"
    15. Re:Sitefinder gives ideas about BIND enhancement by pod · · Score: 1

      Bottom line is, this functionality does not belong in DNS. It is up to the individual applications to do what they think is best when a user tries to communicate with an invalid host. IRC and FTP connections fail. Web browsers display a search page. Email bounces (albeit with a usually cryptic message). And who's to say that what DNS will suggest is even remotely applicable to the protocol and application at hand?

      DNS is a basic underlying protocol. It doesn't need to be saddled with this extra, mostly useless, functionality.

      --
      "Hot lesbian witches! It's fucking genius!"
    16. Re:Sitefinder gives ideas about BIND enhancement by axxackall · · Score: 1
      I disagree. The current DNS functionality is "lookup for names and addresses", which is based on the exact string comparison, which is just a subset to more genereal search engine functionality - "look up for strings using exact AND approximate comparison".

      With all my respect to the current core functionality of DNS, I do not see anything wrong to extend it by OPTIONAL plugins implemented more lookup rules in addition to the existing ones.

      THEN it will be up to individual applications to utilize those extended lookup methods.

      --

      Less is more !
    17. Re:Sitefinder gives ideas about BIND enhancement by asdfghjklqwertyuiop · · Score: 1

      I disagree. The current DNS functionality is "lookup for names and addresses", which is based on the exact string comparison, which is just a subset to more genereal search engine functionality - "look up for strings using exact AND approximate comparison".

      DNS isn't a subset of a search engine... it isn't a search engine at all. It is just a system to associate simple ascii strings with IP addresses and other network information. It was never meant to be a system that you can type fuzzy queries into and have some intellegence that interpreted your query and tried to give you a set of possible results back.

      With all my respect to the current core functionality of DNS, I do not see anything wrong to extend it by OPTIONAL plugins implemented more lookup rules in addition to the existing ones.

      But the wildards that verisign added aren't optional, unless you've upgraded your DNS server to repair the damage they inflicted.

    18. Re:Sitefinder gives ideas about BIND enhancement by Todd+Knarr · · Score: 1

      If you go to look up a phone number for someone and they aren't listed, you want to be told they aren't listed, not given the number for someone else with a similar name.

      DNS is the phone book of the Internet. What you're describing is nice when looked at just as part of browsing the Web, but not as part of FTP or LDAP lookup or NTP synchronization.

    19. Re:Sitefinder gives ideas about BIND enhancement by axxackall · · Score: 1
      If you go to look up a phone number for someone and they aren't listed, you want to be told they aren't listed, not given the number for someone else with a similar name.

      Exactly the functionality I've missed in North America (In Russia and in some European countries you can do it) - sometimes I want a list of suggested numbers with similar names or with similar functions. "Sometimes" means that it should be an option saying to the directory service to use an alternative set of lookup rules.

      And there is nothing wrong if it will be a part of a directory lookup protocol. The web clients will decide how to use, but the function should come from DNS (or LDAP).

      --

      Less is more !
    20. Re:Sitefinder gives ideas about BIND enhancement by axxackall · · Score: 1
      The exact string comparison based lookup function is a subset of more general set of lookup functions based on various rules, including exact string comparison AND fuzzy string comparison. If you have a problem to understand that then go back to your school and learn your math harder than you did.

      DNS as it is now has not been designed for fuzzy string comparisons. But who told you that it will never be designed that way? It is not deadly frozen protocol and it can get new RFCs describing new extensions and even new corrections. 20 years ago the internet was what? 2000 nodes? And how big is it now? Sooner or later some protocols will be changed to adopt to new scale. Like IP did (ipv4 --> ipv6). It's a matter of time to see new RFCs describing fuzzy search in DNS and LDAP services.

      What Verisign did is wrong just because it's not done through RFCs. If (and only IF) there would RFC allowing them to do that - nothing wrong, As well as nothing wrong to extend DNS with better (but still optional) search algorithms - only if there will be RFC for that. And DNS software vendors will eventually implement it, again if there will RFC for it.

      --

      Less is more !
    21. Re:Sitefinder gives ideas about BIND enhancement by Todd+Knarr · · Score: 1

      Forget that the Web exists. 90% of the Internet doesn't involve the Web. Three-quarters of it doesn't even involve human beings. Therein lies the rub. "Similar function" means different things depending on context. For example, the SNMP client in a LAN network monitoring box has a very different idea of what might be a correct alternative than the program-driven automated FTP application trying to grab today's payroll files or the SCP transfer of a password file. The problem is that DNS doesn't know which one it is, so it can't sensibly pick which one it should assume it's dealing with.

      Correcting typos is simply too application-specific. It's why telephone books don't list possible alternative numbers for misspelled names. If you need to find the phone number for a given name, you look in the phone book. If you need to figure out which name you should be looking up, you call directory assistance or look in the yellow pages or use some other service designed to let you find names.

      This is Verisign's mistake. They took a fundamental lookup service that needs to work correctly for a wide range of applications and proceeded to graft functionality onto it that assumed that it was used by one and only one application (web browsers) and used in one and only one way (a human being watching a screen). The resulting train-wreck was utterly predictable.

    22. Re:Sitefinder gives ideas about BIND enhancement by asdfghjklqwertyuiop · · Score: 1

      The exact string comparison based lookup function is a subset of more general set of lookup functions based on various rules, including exact string comparison AND fuzzy string comparison. If you have a problem to understand that then go back to your school and learn your math harder than you did.

      I don't know what you're talking about when you say DNS's string comparison function is a subset of a more general set of lookup functions including fuzzy comparison. That is completely not true. There is nothing fuzzy about DNS. You ask it to resolve a string with a particular resource record type, and you get an exact match back. There is nothing fuzzy about it. Precise query in, precise results out.

      DNS as it is now has not been designed for fuzzy string comparisons. But who told you that it will never be designed that way? It is not deadly frozen protocol and it can get new RFCs describing new extensions and even new corrections.

      It's a matter of time to see new RFCs describing fuzzy search in DNS and LDAP services.

      Noone can predict the future, but if a standard is developed to allow for fuzzy DNS queries it will most likely be backwards compatible and not a requirement to use. Sort of like how DNS was extended to use all kinds of extra characters (like foreign language characters and underscores) instead of [-.a-z0-9].

      This current nonsense that versign has implemented is completely stupid and was only designed with HTTP and SMTP in mind. And what verisign is doing is not extending DNS at all (see below).

      20 years ago the internet was what? 2000 nodes? And how big is it now? Sooner or later some protocols will be changed to adopt to new scale.

      The internet didn't have to change greatly to accommodate millions of new users. We're still speaking IPv4. Most of the protocols are still the same (DNS, SMTP, FTP...)

      Like IP did (ipv4 --> ipv6).

      IPv6 isn't a hack on top of IPv4. IPv6 is a totally different protocol.

      What Verisign did is wrong just because it's not done through RFCs. If (and only IF) there would RFC allowing them to do that - nothing wrong, As well as nothing wrong to extend DNS with better (but still optional) search algorithms - only if there will be RFC for that. And DNS software vendors will eventually implement it, again if there will RFC for it.

      I don't think that verisign's actions violated and RFCs. Wildcards are a standard. Everyone is angry at what verisign did because it is just plain stupid and irresponsible. And the only way verisign's changes are optional are if you have patched your DNS server to make them optional.

      What you are talking about here, multiple organizations/people developing a coherent standard codified in an RFC is the correct way to extend or develop a new protocol. This is completely the opposite of what verisign did.

  7. Re:Huh? by Dave2+Wickham · · Score: 1

    He's an editor

  8. Yay by CausticWindow · · Score: 0, Flamebait

    Reposting old trolls now, are we?

    --
    How small a thought it takes to fill a whole life
  9. [FB] your sig by Anonymous Coward · · Score: 0
    Windows--The biggest beta test ever conducted.

    Whereas Linux is still not out of alpha...

  10. Seven Stages of the Internet by ubiquitin · · Score: 4, Funny

    1. The distributed network in its infancy is lovingly brought to life by researchers: arpanet is born.
    2. Rapid protocol development as the network begins to start walking: from gopher to httpd to mosaic. Email and usenet populate most universities.
    3. Private enterprise realize the potential and small companies start forming around services and products aimed at network usage. Network usage is a daily exercise for academics and early adopters. Linux arrives and Slashdot's squeaky pubescent voice first heard.
    4. The internet meets the economy and Wall Street goes apeshit. Billion dollar companies are started, sustained, and identified by their position on the network and mindshare of net users. The network is the computer.
    5. Infrastructure buildout is complete, and educated people worldwide use it as a communication medium. Initial high-growth opportunities are gone so Wall Street sours on the newness, returning its attention to fundamentals of profit-grubbing.
    6. Annoying spammers take over, search engines are all manipulated, pop-ups for porn and travel are everywhere, Microsoft mass-marketed virus hysteria takes place, simple hosting efforts become a bitch.
    7. Lawyers and short-sighted opportunists inexorably and slowly strip everything likeable from the network by lawmaking and lawsuits until there is nothing left but death and taxes.

    Shakespeare's As You Like It (Act 2:7) ...man in his time plays many parts, His acts being seven ages. At first the infant, Mewling and puking in the nurse's arms. And then the whining school-boy, with his satchel And shining morning face, creeping like snail Unwillingly to school. And then the lover, Sighing like furnace, with a woeful ballad Made to his mistress' eyebrow. Then a soldier, Full of strange oaths and bearded like the pard, Jealous in honour, sudden and quick in quarrel, Seeking the bubble reputation Even in the cannon's mouth. And then the justice, In fair round belly with good capon lined, With eyes severe and beard of formal cut, Full of wise saws and modern instances; And so he plays his part. The sixth age shifts Into the lean and slipper'd pantaloon, With spectacles on nose and pouch on side, His youthful hose, well saved, a world too wide For his shrunk shank; and his big manly voice, Turning again toward childish treble, pipes And whistles in his sound. Last scene of all, That ends this strange eventful history, Is second childishness and mere oblivion, Sans teeth, sans eyes, sans taste, sans everything.

    --
    http://tinyurl.com/4ny52
  11. Could someone explain... by black+mariah · · Score: 1

    Exactly how the hell is this any different from Register.com's redirected stuff? Or any other webhosts for that matter? Is it ONLY because VeriSign runs the domain names for .net and .com? I really don't understand why this is a problem, and I can guarantee you the overwhelming majority of people seriously don't give a s**t. Can anyone explain it without bringing down showers of FUD?

    --
    'Standards' in computing only impress those who are impressed by things like 'standards'.
    1. Re:Could someone explain... by ubiquitin · · Score: 1, Informative

      Yes, the difference between what verisign has started doing and what the domain name purveyors do is this: instead of just redirecting purchased domain names which have yet to be "pointed to" an IP#, they are redirecting any request for any domain name, in realtime that isn't already registered by use of a wildcard redirect, and furthermore, they are tracking the number of occurrances and origin of these requests with Overture web-bugs. This is a major privacy concern in addition to taking advantage of anyone who places trust in the the domain name architecture to look for a destination site.

      --
      http://tinyurl.com/4ny52
    2. Re:Could someone explain... by boy_of_the_hash · · Score: 2, Informative

      Data mining! They set up a fake SMTP server that dosn't drop the connection until AFTER they have the 'FROM' address. There partners in this sitefinder are overture, how is this FUD?

    3. Re:Could someone explain... by black+mariah · · Score: 1

      I don't see how that's a privacy concern any more than any other website logging IP's is. What, are the Internet Police going to come and beat my ass for misspelling 'slashdot.org'? ;)

      Okay, serious now. I've run into Sitefinder a few times. I really don't see what the big deal is about. When you make a mistake it redirects you to a page that lists domain names close to what you were looking for. I find this a lot better than register.com's popup laden crap, or anyone elses for that matter. I don't see how tracking the number of occurences and origin of a misspelling is a privacy concern. I'm sorry, none of this makes any dent on my web browsing and if it doesn't bug me (a techie) then why the hell should the general public (who don't care about anything technical about the internet) give a rat's arse?

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    4. Re:Could someone explain... by Anonymous Coward · · Score: 0

      why don't you crawl back where you came from? foly shit, you are a techie? what for, cars?

      none of this makes any dent on my web browsing

      blablabla, noone cares about your "web browsing" experience, aol loser. there are people with real installations and applications that are fucked by this marketing bullshit.

      please don't go about claiming you have any insight about how the internet works.

      where the fuck do these people come from?

    5. Re:Could someone explain... by LostCluster · · Score: 4, Interesting

      Register.com simply put up a test patern page by default when somebody registered a domain but failed to come up with with valid nameservers. That was annoying to those who paid for domains they weren't using, but then again its also their fault for not having one of the reqirements it takes to operate a domain.

      This is different because Verisign isn't limiting their actions to domains registered through them. In fact, SiteFinder replaces every domain in .net and .com that hasn't been registered, which is something only VeriSign could possibly do.

      Basically, SiteFinder's IP address is being returned any time a .com or .net query is supposed to return "NXDOMAIN", an indication that the domain doesn't exist and therefore the request is no good. That was an error that used to be handled by the user's software, now Verisign has overtaken that.

      This breaks any application that depended on "NXDOMAIN" accurately being reported. One key application was an important spam defense... if the domain in the from field returns an "NXDOMAIN" when somebody tries to look it up, trash the message because the from line must be bogus. Now, nothing returns "NXDOMAIN" when queried, so that test always returns a negative.

      ICANN hired VeriSign to run the DNS system according to the protocols. This is something that's not in the protocols, and VeriSign is just doing with a "You can't stop us!" attitude. ICANN nicely asked VeriSign to suspend the service, and got a defensive reply. It's time for either ICANN to fire VeriSign, or for the US Dept. of Commerce to fire ICANN...

    6. Re:Could someone explain... by Reziac · · Score: 1

      "I don't see how tracking the number of occurences and origin of a misspelling is a privacy concern."

      It's not primarily a privacy concern as such (unless you typo'd hotkiddiepr0n.com or ihaveaids.com and wound up at Sitefinder instead, IP address in tow). However, it IS a concern if they correlate typoes, and decide that goggle.com looks like a good one to squat on and sell to the highest bidder. Which, IMO, is what this is *really* all about.

      There are already domain squatters who have a nice form for folks to check whether a domain is available or not -- if enough people query about a given domain, intentionally or otherwise, doncha think they can take the hint??

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    7. Re:Could someone explain... by black+mariah · · Score: 1

      If you're going to start shit, have the balls to do it when logged in you pussy-ass bastard. Then again, you can't spell and apparently have no clue what the shift key is for so I doubt you're anything more than a fucktarded troll. Go blow some goats.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    8. Re:Could someone explain... by Anonymous Coward · · Score: 0

      ICANN didn't "hire" and cannot "fire" Verisign. I too wish they would assign com and net to another registry though.

  12. Register.com might be next by GeorgeK · · Score: 4, Informative

    Register.com might be the next one to file suit, given their strongly-worded letter which was sent to VeriSign and ICANN.

    The Stop Verisign DNS Abuse Petition is still going strong, with 15,000 signatures. ICANN still hasn't had the sense to post it on their website, though. They have a public forum at the very bottom of the page here at least, with 64 comments (many from the petition site, as we're giving folks the option to forward those along to ICANN too).

    1. Re:Register.com might be next by jimhill · · Score: 1

      Have you corrected the spelling of the message forwarded to ICANN? I have no intention of sending them an email that says "I have signed an agree with blahblah." What the hell is an agree?

      --
      Learn to spell: nickel, missile, lose, solely, amendment, speech, kernel, probably, ridiculous, deity, hierarchy, versus
  13. Some hit stats from sitefinder by Chatmag · · Score: 2, Informative

    I'm not happy with sitefinder, but I have seen some referrals from misspelled names to our main site. Not a lot, but enough to get noticed. What I also notice is that several domain names that I previously owned, but not owned by anyone at the moment, are all coming up as a sitefinder page. I just wonder if they are doing this to all expired, previously registered domain names. And for the record, the domain names were originally registered on Network Solutions/Verisign.

    --
    Pete Carr Owner Chatmag.com
    1. Re:Some hit stats from sitefinder by rufey · · Score: 1
      VeriSign *IS* applying this to all expired but previously registered sites.

      I know this because last weekend we got bit by this. We had a monitoring script that checked whether or not one of our web sites was in DNS. In a bizzar set of circumstances, the domain had expired 6 days prior to this. We didn't receive any email or snail mail notices about this, and it was only after 6 days had passed since the expiration that VeriSign sent an email to the admin handle, et al.

      By that time customers were calling us asking us why this "sitefinder" page was coming up instead of the usual pages.

      It took a little bit to figure out what had happened, and then fix it (registering a domian doesn't make it immediatly appear in DNS....). We have since ensured that all of the domains we own are on auto-renew.

      In summary, if a site has been expired for as little as 6 days, VeriSign returns the Sitefinder IP instead.

  14. Great, a class-action suit. by anon*127.0.0.1 · · Score: 4, Funny

    Let me guess... it'll be settled out of court, Verisign will admit no wrongdoing, the lawyers will get a few million dollars, and we'll all the $5 off the next domain we register with Verisign.

    I can hardly contain my enthusiasm.

    --
    I am NOT a man!
    I am a free number!
  15. Big Problems? by tarnin · · Score: 4, Insightful

    I see big problems arising from this. One, if it looks like VeriSign will lose, they will more than likely settle out of court and make sure an issue like this stay untested as to be lawful or not. Just like the DMCA mess and the mass suing from the RIAA.

    Second, VeriSign is handling the .com/.net domain on good faith really. No one has the power to remove them from handling these domains. There is no true law up to this point on who owns them and what guidelines they HAVE to follow. Even the RFC's don't contain any insight on how something like this should be handeled.

    Do we really want the gov (at any level) to start getting their hands in this? Do we want another self appointed body saying what can and cannot go? Both of which, to me, are scary but it seems that the "self healing" that the internet was built apon is failing at this point. Even if another RFC is written, who's to say that VeriSign will follow it?

    I see no good comming from this really. The only good ending would be that VeriSign halts its practice on its own and an RFC is drafted to prevent this in the future and people follow it. The only issue I see there is it's still done on faith and it looks like faith has gone the way of the dot.coms.

    1. Re:Big Problems? by LostCluster · · Score: 3, Informative

      Second, VeriSign is handling the .com/.net domain on good faith really. No one has the power to remove them from handling these domains. There is no true law up to this point on who owns them and what guidelines they HAVE to follow. Even the RFC's don't contain any insight on how something like this should be handeled. .com and .net are really properties of the US Dept. of Commerce. DoC has a contract with ICANN to provide this service, and ICANN has a contract that makes VeriSign the authoritative servers for .com and .net. VeriSign once upon a time had control of .edu, but they lost that. The same thing can happen to .com and .net if they act too stupid.

    2. Re:Big Problems? by Sphere1952 · · Score: 2, Insightful

      "Do we really want the gov (at any level) to start getting their hands in this?"

      Um... The Internet was _created_ by the military (DARPA); which is part of our government. It used to be called ARPA Net.

      DARPA decided it didn't want to be the owner of the Internet and stuck the Department of Commerce with the problem. DoC didn't want the headache either and set up ICANN; which it has been trying to hand the Internet to for years.

      It seems to me that the gov already has its hands into this rather deeply, and now is not the time to let them wash their hands.

      --
      Big Brother Bush is doubleplus ungood.
    3. Re:Big Problems? by gothicpoet · · Score: 3, Insightful
      A little history lesson seems to be in order.

      The government created the Internet. The government ran everything until the Internet was commercialized. Verisign got the position they now have when it was relinquished by the government.

      We didn't have this problem when the government was running things.

      The Internet is one of those cases where the "government is always bad" dogma is way off course.

      --
      Quoth he ::
      "It's all academic anyway..."
    4. Re:Big Problems? by tarnin · · Score: 1

      I know that the gov created it to use for the ability to communicate and trasfer information incase of war. I belive everyone knows and understands that but it as grown well out of those early days and is now a freeflowing form of its former self.

      Of course no one cared at the time, no one either knew about it or was using it outside of a select few schools and the gov itself. Now that the WORLD is using it it's a totally different story.

      As I asked before, do you really want the gov to get involved with this or to put it more perciscly, with the internet the way it is TODAY.

    5. Re:Big Problems? by SEE · · Score: 2, Informative

      Do we really want the gov (at any level) to start getting their hands in this? Do we want another self appointed body saying what can and cannot go?

      VeriSign runs .com and .net under a contract with the U.S. Department of Commerce. Similarly, ICANN is *not* self-appointed; it was appointed by the U.S. Department of Commerce. The government is already in this up to its elbows.

    6. Re:Big Problems? by Loconut1389 · · Score: 1

      Firstly, when it was 100% government on the ARPA net, everyone with access was supposed to have access and if they messed with it they would be court marshalled. Secondly it obviously wasnt commercial and so greed never entered in as a reason for major change. Thirdly, there weren't enough people, or for that matter malicious people, who were on the net. Its apples and oranges. The internet was to ARPA as intranets are to us now. It would be like sabotaging your company network, and being dishonorably discharged for treason/sabotage.

      I think that 'we didnt have this problem when the government was running things' is fairly irrelevant because things were so different.

      I do however agree, the government is and always has been a saving grace in a lot of situations where something is simply too big for 'the people' to manage or for 'the people' to really be able to individually make a difference with regards to a desire of theirs or an annoyance.

  16. No DNS entry for a domain - still redirected by Flopper · · Score: 1

    Hm. I seems every domain owner who has disabled his DNS entry could go into such a lawsuit, couldn't he?
    VeriSign does redirect the domain he buyed for the use permission just because no DNS entry is present.
    At least already registered domains with just no DNS delegation should be excluded.

    Same is the case with every TLD which does make use of the same feature so I agree on this point really. Making not-registered domains valid does break services so it's generally a No-No. IMO ICANN should give any resolution out on this matter.

  17. Join it! by davetrainer · · Score: 2, Interesting

    IANAL of course and most of you probably aren't either, but if you really detest VeriSign then don't just rant about it on Slashdot, join the lawsuit. It doesn't take much of your time, is a learning experience, will make a real difference by strengthening the case against VeriSign, and there's a slight cance it will actually net you some cash.

    The catch, of course, is that you have to fit the description of the proposed class, and this story is short on details regarding what that proposed class is. I can only speculate that it would be anyone who has typed a URL lately and ended up at SiteFinder when they expected to find something else.

    1. Re:Join it! by dzym · · Score: 1
      I would, but I can't seem to find information on where and how to join this class-action lawsuit.

      Perhaps someone would care to enlighten us?

    2. Re:Join it! by Sphere1952 · · Score: 1

      "...ended up at SiteFinder when they expected to find something else."

      In this case, the something else is nothing; which is exactly what you want to find when checking an invalid return address.

      --
      Big Brother Bush is doubleplus ungood.
    3. Re:Join it! by FLEB · · Score: 1
      --
      Information wants to be free.
      Entertainment wants to be paid.
      You just want to be cheap.
  18. ICANN accepting comments by turg · · Score: 2, Informative
    I for one will be happy to see VeriSign blasted on this one

    Well, blast away . . .

    ICANN is accepting comments on Sitefinder. This page also has links to various official letters they've received.

    Also, Lauren Weinstein 's People for Internet Responsibility is looking for data on the effects of sitefinder
    --
    <sig>Guvf vf abg n frperg zrffntr
  19. What do you WANT to happen? by sethadam1 · · Score: 1

    I don't care where it's settled.
    I don't care who makes or pays money.
    I don't care if I get a discount on domains.

    I just want that fucking Sitefinder disabled.

    How 'bout you?

    1. Re:What do you WANT to happen? by Anonymous Coward · · Score: 0

      Having sitefinder disabled would be nice. But Verisign has been making a list of all the domain names that are funneling into sitefinder, and how many hits each get. So even if sitefinder gets shut off tomorrow, they'll have a nice list of popular domain misspellings that they can register or sell or somehow make some more money off of.

      So what I'd really like is for Verisign to be forced out of business, or at least out of the domain registry business. Failing that, I'd like to see that "The Value of Trust" logo jammed up their collective asses.

    2. Re:What do you WANT to happen? by Anonymous Coward · · Score: 0
      But Verisign has been making a list of all the domain names that are funneling into sitefinder

      yes, this is why i run a cron job that looks up variations on domains with the words "farm animals" "sex" and "warwick". (last time i checked, warwick ford was CTO of verisign)

  20. Awwwwww by Tirel · · Score: 0, Troll

    What is this now? You bit and now you're feeling stupid for responding to such an obvious troll?

    Shit, it only took 3 reposts for you to get it (and who knows how many times before by the guy who originally wrote it) !

    A thought is resounding in my mind right now... YOU ARE A DUMBASS. But hey, you can always claim vlad-style retroactive trolling!

    1. Re:Awwwwww by KrispyKringle · · Score: 1
      No, I know a troll when I see one. I posted because I didn't want others to think it was a good idea. I'll give you that much credit that you managed to fool a few dumbasses with mod points on slashdot. Whoop de do. Your life is complete.

      Seriously, though, I really am curious what sort of silly pleasure you get out of this. Why is trolling so much fun for you? And, if you don't mind my asking, are you 13 or not? Just curious.

  21. What happens to registration fees? by Anonymous Coward · · Score: 0

    Does Verisign (and others) keep 100% of the fees they charge for registering a domain?

    If not, perhaps Verisign should pay for all those domains they now host! A penny per domain name would be fine...

  22. Re:Huh? by Anonymous Coward · · Score: 0

    he's a gross, fat, ugly, dirty, dick-licker!

  23. Hi$story of using $ for S by Felinoid · · Score: 1

    Compu$erve got this LONG before Micro$oft was anything evil.
    Back in the day Compu$erve was basicly a large mainframe (Compusere had been in business for a VERY long time) and at the time BBSes were everywhere.
    The problem was that Compuserve had become very expensive for the time due to charging an hourly rate and most of Compuserves services were available for free from BBSes.

    People had gotten tired of it and started calling it Compu$erve.

    Now a days Microsoft basicly overcharges for Windows for what they get for free with Linux.

    --
    I don't actually exist.
  24. Let's see.... by dacarr · · Score: 1

    Verisign now has not only ICANN telling them to stop, but three suits against them for doing this crap. They won't get the message, but perhaps they will stop this and remove the wildcard from their root if the suit is found not in their favor.

    --
    This sig no verb.
  25. What bugs me about it... by MadAnthony02 · · Score: 1

    when you mistype that domain name, you get a few suggestions. You also get a list at the bottom of the box for "popular searches". Click on them and you get "sponsored results for:" listings. Sponsored results means they are making money off of this via their "monopoly" on the fact that they run the DNS.

    Of course, it's a messy fight, because VeriSign wants to make money off people clicking on the links that display because of their position of power, while the companies suing like Netster want to make money by buying mistyped domain names, then inflicting 18 popups, a homepage redirect, and a copy of Gator on you. So no matter who wins, we lose

    1. Re:What bugs me about it... by black+mariah · · Score: 1

      I'd rather lose to the tune of a page with sponsored links than lose to 18 popups, gator, and having my homepage changed. There are some levels of BS you have to put up with, and I'll take SiteFinder over Netster any day of the week.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
  26. Get a clue Verisign Lawyers by ac7xc · · Score: 1

    How many lawsuits will it take Verisign to get the hint that they can't do this? I'm just waiting for the trademark lawyers to start filing lawsuits next. Verisign balance Sheet: Income 1,000,000 Expenses 2,000,000 (1.5 million went to lawyer and settlement fees.)

  27. Coercion by Anonymous Coward · · Score: 0

    Interesting how the only gendre founded in genuine scientific origins (sci-fi channels) have the most obnoxious, sterotypical, aggressive propaganda (commercials) which have nothing to do with the viewer other then to piss him/her off. Coupled with a less then average social life. You either end up with a criminalized profile (with irrational tendencies towards a decided scapegoat).

    Coercion???, who/why/when.

  28. Is it the user's decision? by Anonymous Coward · · Score: 0

    Do the users get to decide that the internet will be full of scamming and abuse? I think not. It is up to the courts to decide this. Companies must obey the law, and people who use the internet will get along with whatever happens, because people are very adaptive. However, the legalities of the system must be observed. If they are not, what good is a judicial system?

  29. ISPs abuse the system too by dilute · · Score: 1

    Fundamentally, I think some of the complainers here are just bitching because Verisign grabbed for itself the ability to scam via redirection that these folks previously were independently making money off of.

    This sort of bogus redirecting is rampant. Not just with people who hoard typo domains, but with more "reputable" companies such as major ISPs.

    I still haven't gotten to the bottom of this one, but when my machines were set up to get their DNS settings via DHCP, I would find weird "search" directives inserted into my resolv.conf files, to some name server within my ISPs address space, I believe (this is with TWC-Roadrunner), with the result that my browser would get redirected whenever I picked a page (even a properly spelled one) from my recent history list. This was happening on every machine on my LAN when they were running Mozilla-Firebird. Every frigging time you tried to go to a page via the history drop-down list, you'd end up at Web100.com or worse. I never completely figured out what was going on, but when I switched everything to static addressing on the workstations (that is, behind my NAT box) and hard-coded resolv.conf to delete any "search" directive and simply point to known, non-bullshit name servers, the problem went away.

    Commercial companies abuse their superior position on the network all the time to take advantage of those below them on the food chain.

    Verisign isn't the only one or the main one, just the one in the best position to trump everybody else. Perhaps letting them do it and control it is better than the alternative, which is a free for all. The way the current system is set up there must be a root server, and someone has to control it. Do you really think the GOVERNMENT would do a better job?

    1. Re:ISPs abuse the system too by Anonymous Coward · · Score: 0

      You don't know what the search directive is for, do you?

      It's like a search path, for domains. So if the search has 'internal.isp.com isp.com' in the search path, when you type in the URL something like 'www' the resolver will look in the search path, and try to first resolve www.internal.isp.com, and failing that will move on to www.isp.com. That Mozilla is fucking up and taking you to the wrong site is hardly your ISPs fault. Get a browser that works properly.

    2. Re:ISPs abuse the system too by Ice_Balrog · · Score: 1

      About Mozilla Firebird:

      In some cases, if you get s NXDOMAIN responce, Mozilla Firebird will do a Google "I'm feeling lucky" search. In some cases, Web1000 happens to be the site that Google turns up. Thus Firebird goes and sends you to that site.

      --
      #include "sig.h"
    3. Re:ISPs abuse the system too by dilute · · Score: 1

      Actually, I didn't - I looked at some docs at the time but didn't see anything for 'search'. Thanks for the explanation - seems straightforward, what you would expect. Anyway, I'm talking about clicking on perfectly good URLs like www.slashdot.org clicked on from the address bar history drop-down. When I get rid of the 'search' directive in resolv.conf the browser behaves properly and goes to slashdot. With 'search' it goes to web1000. I don't think the response below explains it either. Maybe it is just the browser, I don't know.

  30. Expectations Broken by The+Famous+Brett+Wat · · Score: 2, Informative

    As Paul Vixie said, the major problem here is one of broken expectations. The .com and .net domains have behaved in the non-wildcard manner since day dot. There is a reasonable expectation that a DNS query on a non-existent .com or .net domain will return a "no such domain" response. VeriSign unilaterally broke this without warning. I believe that ".museum" has implemented the wildcard since day dot, so there are no broken expectations there. As the IAB said, it's reasonable to implement wildcards with the informed consent of everyone who is delegated a name in that zone (but it's still a bad idea, technically, for various reasons).

    --
    proof, n. A demonstration that a conclusion is implied by certain premises and axioms.
  31. More links by EddydaSquige · · Score: 1

    The email that Go Daddy sent its customers can be found here and their complaint against Verisign can be found here.

  32. What really steams me is... by nobodyman · · Score: 1
    Their Terms of Use page. I love this part:
    By using the service(s) provided by VeriSign under these Terms of Use, you acknowledge that you have read and agree to be bound by all terms and conditions here in and documents incorporated by reference.

    So basically, they've hijacked my browser to take them to their site, and then claim that my use of their "service" contractually binds me to their terms of use. Nice. Make sure you type your urls very carefully lest you become contractually obligated to Verisign!

  33. No Shame - Revisited by Anonymous Coward · · Score: 0

    Lawyers who bring these actions truly have no shame, but the reason they can get away with this is simple: most people on the net now are new to it, and have not the faintest idea about how the net used to be a cooperative medium, where bullshit like this was not tolerated. Today? No such luck, users expect to be scammed and abused with every click, they will accept this, and they are the majority.

    Here's the real shame: The 5 step program for building wealth in your lifetime:
    1) Goto School - Get your JD
    2) Pass the bar
    3) Join ABA
    4) File class actions
    5) $Profit!

    Nobody involved in this class action appears to want to see YOU get the money. This is for the lawyers and the lawyers only... get that through your thick heads and you won't keep cheering this litigation crap on.

    Look at the other two parties who are suing Verisign and you might just see a pattern.

    Figure it out now and your life will be happier: Lawyers who enter into class actions are generally never heroes of the little guy. Though they now seem to work on increasing their PR and public appeal on "news" networks, hosted by a lot of... lawyers (well, at least those anchors are off the streets and out of the court rooms)!

    Law license in the hands of the people doing the suing generally = License to harass, license to scam. Check it?

    Prospect: Verisign
    Large company - Check
    Deep pockets - Check
    Cash flow solid - Check
    Has adequate incentive money : settle ratio to make an action profitable - Check
    Can be vilified by gullible nerds so as to deflect the real reason for the action - Check
    Conclusion: Excellent Target
    Likely outcome for council: $Profit$

    The lawyers sue, gain wealth and you will pay for it, not benefit from it. Going to court is not a damn lottery (unless you have that JD, that is)!

  34. GoDaddy by sharkey · · Score: 1

    Is anyone having difficulty resolving domains and hosts registered through GoDaddy?

    --

    --
    "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  35. Bogus.Museum and other Wildcard TLDs by billstewart · · Score: 1
    There are a couple of ccTLDs that have supported wildcards, as well as .museum doing that. I can't check which ones any more because my ISPs seem to have all installed the BIND patch that makes them disappear :-) I'm not aware of any of them besides Verisign's .com and .net that have catchall mail servers as opposed to just catchall web servers, but there may be some, and it's a problem either way.

    But yes, spammers can do this with those ccTLDs, and the fact that it's an obvious problem when .com and .net do it doesn't mean we shouldn't have realized it was a problem when .museum and those ccTLDs did it. (oops...)

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  36. *.root-servers.net are also at fault by billstewart · · Score: 1

    Verisign is responsible for the Registry, which is the official database of .com and .net domain names, IP addresses, and whois information, but the Root Servers actually implement the DNS. Aren't they also responsible for making sure their config files are correct (and *.com is obviously an error)? Some of them are run by Verisign, but some aren't, including some outside the US, and even some by Paul Vixie, the author of BIND who did the recent patch that made it not accept Verisign's bogus data. This may change the _operational_ issues, but they still should be doign the Right Thing.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  37. Registry vs. Registrar by billstewart · · Score: 1
    Verisign runs the Registry which keeps the master database that all the Registrars use when they're selling .com and .net domain names. Verisign is also a Registrar, but this is a Registry problem, not a Registrar problem.

    That doesn't mean that you can't argue that Verisign doesn't owe somebody (themselves?) $6/name for the previously-unregistered names they're now using, or that they don't owe ICANN whatever cut ICANN gets of those names....

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  38. Sitefinder != DNS by billstewart · · Score: 1
    You probably meant "one who can afford expensive lawyers"?

    No, a DOS on Sitefinder's IP address, which is what a DOS on bogus .com domain names would accomplish, wouldn't affect the root name servers. It would interfere with reaching their web search pages and email trap pages, taking longer for bouncegrams to get back, which is still bad, but it wouldn't bother DNS at all. And of course, it would still be Wrong and probably illegal.

    Now, if you want to have fun with SiteFinder's email system, you can start leaving a bunch of bogus-domain email addresses around for spammers' harvesters to pick up. That would mean they'd be more likely to send their spams for random users or dictionary-attack to SiteFinder instead of real machines, but presumably Verisign sized their systems to account for this.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  39. Ticked at VeriSign? Tell these people! by SEE · · Score: 2, Informative
    1. The Department of Commerce; VeriSign's contract to operate .com and .org was originally with them.
    2. The Federal Communications Commission, which oversees telecommunications.
    3. The Senate Commerce Committee's Subcommittee on Communications; contact the committee itself, the chairman, the ranking member, and any of the other members you'd like.
    4. The House Subcommittee on Telecommunications and the Internet, including the committee itself, the chairman, the vice-chairman, and the ranking member. Plus any of the other members you feel like contacting.
    5. The Federal Trade Commission, which hears consumer complaints.
    6. Your U.S. Representative
    7. Your Senators
    8. Your Governor
    9. Your State Legislators
    10. ICANN's wildcard comment address
    11. VeriSign itself
    12. Finally, complain to the media. If they get lots of letters on a topic, they'll run stories. Try the New York Times, the Washington Post, the Washington Times, the Los Angeles Times, USA Today, the Wall Street Journal, CNN, Fox News, CBS News, ABC News, NBC News and MSNBC.

  40. Re:Big Problems? (Pardon the windy response...) by gothicpoet · · Score: 2, Informative
    The government is already involved.

    Who set up the contract with Verisign? The "gov" did. Who kept the contract with Verisign? ICANN, but who set up ICANN? The Department of Commerce -- the "gov".

    Do I want to see the government directly administrate this? No. Do I want a for profit company to be granted the monopoly that Verisign has? HELL, no. I think the second option is actually worse in the long run.

    Personally I think that a non-profit organization should be doing what Verisign has been doing. It's a monopoly position and as such can't be trusted to a "for profit" entity (IMHO for whatever it's worth). There's no danger of them being beaten by "competition" so there's no incentive for them to do a good job and follow the rules. If they screw everyone else over, "so what? It's our playground."

    But to question whether we want the government "involved" seems a little naive. The government has always been involved, is still involved, and frankly will probably always need to be involved.

    The government was heavily involved up until well after the Internet went into wide use. The the Clinton folks decided to try to turn it into just a cash cow. Unlike some people, I tend to like a great deal of what the two Clinton administrations accomplished... but this whole business of trying to turn the Internet into nothing but a commercial space was foolish. The Internet isn't a street market.

    Then again, I suppose the government had a lot of help from all the profiteers until the bust.

    The Internet is a community. Every community has a place and need for businesses. Every community also has a place and need for government.

    Business' interest is in making profit. It isn't interested in handling bad actors. The market will to some extent correct for bad actors but will also encourage bad actors to some extent. Just look at the business headlines of the past couple of years.

    And in some cases bad actors pop up who the market could care less about because their actions don't involve money. Government is the third party that has the job of stepping in and controlling the bad actors (in or out of business) and imposing ethics on business.

    This particular situation with Verisign involves a monopoly. Sometimes a monopoly is unavoidable. Like with power companies, this is one of those situations. Also, like with power companies, there's a necessity for a governing body that is NOT (at least not entirely) made up of commercial interests.

    ICANN should be filling that role but it's track record is abysmal and it's causing all of us to reap what they've sown.

    When you've got a monopoly resource you can either have government manage it, a business handle it, or a non-governmental non-profit organization handle it. It can certainly be argued that government isn't always the best way to go. Alternately, giving a business a monopoly removes the only check on bad behavior -- competition. If there's no competition, sooner or later government will have to step in and either reign in the business or take over because the business will abuse the privilege of it's position.

    How soon it happens depends on the ethics of those initially in charge, but sooner or later there'll either be overt abuse of power or simply really shitty customer service and bad management of the resource. There's no incentive to avoid it.

    Unfortunately, to some extent, no matter who "manages" the monopoly community resource, there's going to have to be a level of governmental oversight, or there will be Verisigns all over the place saying, "You don't like it? Then don't use our service. Oh, you can't avoid our service if you use the Internet? Well, there's your answer, bub."

    --
    Quoth he ::
    "It's all academic anyway..."