Slashdot Mirror


Passport to Nowhere

prostoalex writes "CNET News.com.com talks about less than glamorous acceptance of Microsoft's single sign-on technology, .NET Passport. Being launched as a single sign-on service for online businesses and competing heavily with open Liberty Alliance project, which so far has produced just a large amount of PDF files, .NET Passport is considered a failure (although not by Microsoft). Turns out, high licensing fees, lack of simple implementation, security leaks and server downtime, were not acceptable to most of potential clients out there."

31 of 361 comments (clear)

  1. Favorite quote from TFA by Liselle · · Score: 5, Insightful

    "Microsoft was kind of pushing Passport for a problem that didn't exist..."

    I think that more or less hits the nail on the head. This is aside from the downtime issue, which is embarassing, and privacy issues, which are disturbing. On the privacy/downtime note, the Liberty Alliance may be vapor currently, but the idea of a "federated" system sounds much better to me. It's not a problem I have with Microsoft, rather it's a problem I have with giving all of my personal information to a single organization to put into a central respository.

    No sir, that's bad sauce.

    --
    Auto-reply to ACs: "Truly, you have a dizzying intellect."
    1. Re:Favorite quote from TFA by michael+path · · Score: 4, Interesting

      I had that quote cited and ready to post as well.

      It's still not an issue that exists today. However, I'm an avid user of Paypal because it's more convenient to pay with my username and password submitted only to Paypal's server, and let them return the "Success/Fail" of the payment to the vendor. It made eBay easier. It's easy to subscribe to Slashdot/OSDN using it. It's easier to subscribe to some porn sites using it.

      Granted, that's just the payment piece, and not the cetnralized repository of all my useful details - but significant just the same.

      Now, if Microsoft bought eBay (and thereby, Paypal), they'd have an existing solution they could extend to suit their needs.

      That said, the moment Microsoft buys eBay is the moment I evaluate auction alternatives.

    2. Re:Favorite quote from TFA by PacoTaco · · Score: 4, Insightful

      Microsoft wants to push the distributed web services model. Web services are much easier to manage with a centralized authentication system (rather than dealing with many separate passwords/certificates per application). Whether something like Passport is right for end users is another question.

    3. Re:Favorite quote from TFA by Otter · · Score: 4, Interesting
      "Microsoft was kind of pushing Passport for a problem that didn't exist..."

      I wouldn't say the problem doesn't exist -- every time a link takes me to an article at the LA Times, Chicago Sun, Telegraph or any other paper that requires me to remember some crazy new userid or to go through a lengthy registration process, there's a problem, usually solved by my deciding it's not worth it. Or bidding on eBay from the library, or...

      As you say, a central repository seems like a bad solution but I'd really love to have a good one. (And, no, my having to carry everything around on a memory stick is not a good answer. For one thing, you can't just mount them anywhere.)

    4. Re:Favorite quote from TFA by TrentL · · Score: 5, Funny

      I just use a dummy password for all those newspapers anyway. I let the browser remember it.

      Oh, and I'm not a 65-year old CEO living in Ethiopia, but don't tell that to the Washington Post.

    5. Re:Favorite quote from TFA by Sigma+7 · · Score: 4, Insightful
      Whether something like Passport is right for end users is another question.
      While I'm not speaking for everybody, I'm sure there's a large group of people that always hate having to register for every individual website for the sole purpose of posting a single comment. It's one of the many good reasons why Usenet is still around. It's also the same reason why Gamespy's Forumplanet is keeping so many users in spite of having a poor forum interface.

      Multiple logins aren't better either. Given the sheer quantity of internet forums, a user will eventaully give up on creating new username/password combinations that they will simply recycle them (a big security risk right there.)
    6. Re:Favorite quote from TFA by Jim_Maryland · · Score: 4, Insightful

      "Microsoft was kind of pushing Passport for a problem that didn't exist..."

      The problem of single sign on (SSO) does exist, particularly in the corporate world. Vendors implimenting Web Portals (MS SharePoint, Sun Java System Portal Server, BEA WebLogic Portal, Vignette Portal, etc...) have a particular interest in SSO and identity management via Identity Services to present a single interface to various systems in an enterprise.

      My main problem with MS Passport is that it's Microsoft's version of a standard rather than a community standard. Applications can connect via MS's SDK rather than publishing the standard. Using Open LDAP, Sun's Identity Server, etc... will generally follow open standards and have better compatibiltiy to other open source/standard applications.

    7. Re:Favorite quote from TFA by 1010011010 · · Score: 4, Insightful

      PassPort? Jeesh - you /. dorks will replace a simple 2 second process with one incredibly difficult and annoying just to stay away from MS... You may think you're some sort of "Freedom Fighter", when really you're just a retard.

      How's the weather in Redmond?

      I'm sure PassPort will protect you from spyware, such as keystroke loggers, on those public terminals, right? And I'm sure that giving MSFT control over my personal authentication tokens is really in my best interest, never mind passport's publicised security problems. Yeah, I'm the retard for not trusting it.

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
  2. Personally.. by Caedar · · Score: 5, Insightful

    I never saw a need for .NET Passport in any way. Privacy issues aside, all Passport would achieve for the company using it is something they could already do with simpler, more secure, and less liable technologies already available to them.

  3. Hmmm by Anonymous+Crowhead · · Score: 5, Funny

    Turns out, high licensing fees, lack of simple implementation, security leaks and server downtime

    Yet they still buy windows...

  4. "Competing Heavily"? by American+AC+in+Paris · · Score: 4, Insightful
    [.NET Passport is] competing heavily with open Liberty Alliance project, which so far has produced just large amount of PDF files

    ...by this logic, one could say that Halo is competing heavily with Duke Nukem Forever, or that Coca-Cola is competing heavily with Cola Turka...

    I mean, doesn't "competing heavily" imply that there's, well, an active competition in the first place?

    --

    Obliteracy: Words with explosions

  5. Only used in hotmail by sapped · · Score: 5, Informative

    I actually created a passport login to see how many places they would use it and if it would be beneficial. Thus far I have only seen it used with Hotmail and on the MSN site. Have any others seen it used on other non-Microsoft sites?

  6. No thanks by Orien · · Score: 4, Insightful

    I like the concept of passport, but I'm not going to get in bed with Microsoft to put it on my web servers. Besides, it has always seemed to me that doing a scheme like that would introduce so many more points of failure to your web system, that it wouldn't be worth the trouble. That's not to mention security. Somehow I just feel safer when I have to log in to each site separatly.

    1. Re:No thanks by AnotherBlackHat · · Score: 5, Insightful

      I like the concept of passport ...


      The entire concept is flawed from the get-go.

      If I wanted my passwords stored on a computer, then I might as well do away with them completely.

      But assuming I did want to to store my passwords on a computer, I'd want them on my computer.

      And if for some reason, I wanted to store them with a third party, I wouldn't want the storage to be a single sourced service.

      And if was willing to accept a single sourced service, I still wouldn't want that source to be Microsoft.

      And assuming you get past all of the above, you still need to convince the vendor that it's good for them too - and you'll need to convince a lot of them to make it worth while.

      -- this is not a .sig
  7. Just PDF files? by finkployd · · Score: 5, Informative

    Liberty Alliance project, which so far has produced just large amount of PDF files

    Which is all they intended to produce. Technically Liberty Alliance is a spec, not an implementation.

    Now if you are asserting that there are no implementations, the SourceID people would probably disagree with that.

    Finkployd

  8. 2 Things by panthro · · Score: 4, Funny

    1. I have yet to meet someone who actually has (let alone uses) a .NET Passport.

    2. If you are thinking about replying to this message with "I Do!", then I probably won't meet you, so see 1.

    --
    If you're not part of the solution, you're part of the precipitate.
  9. Concept Good, at first. by jolyonr · · Score: 5, Insightful

    At first, the concept of a global authentication system seems great. We all have too many passwords to remember, the idea behind Passport seems great.

    But in reality, there isn't anyone who is secure enough, trustworthy enough, powerful enough and smart enough to pull off a system that would work and would be trusted.

    You need to have the strength and power to be able to build such a system, and with those, trust invariably goes out of the window.

    So for now I'll keep all my passwords in my brain, and pay the price of my mistrust.

    Jolyon

    --


    Please read my Canon EOS tech blog at http://www.everyothershot.com
  10. Re:Microsoft and the FBI by Anonymous Coward · · Score: 4, Funny

    Interesting claim. Care to, you know, back it up with something?

    Back it up? You must be new here.

  11. Vendors don't want it. by AnotherBlackHat · · Score: 4, Informative
    From the article

    "I can't imagine a Web site today being willing to pay $10,000 a year and go through the whole process necessary to implement Passport."


    Hello? It's not very easy to imagine a site that's willing let a third party handle customer information for free.

    Most companies aren't even willing to tell you how many customers they have, much less let you collect personal information about them.

    -- this is not a .sig
  12. Re:Problem that doesn't exist big time... by jfengel · · Score: 4, Informative

    The problem isn't managing passwords for a web site. The problem is managing passwords for ALL web sites.

    How many accounts do you have, between eBay and paypal and Amazon and slashdot and ...? Do you use a different password for each one? Aren't you the least bit worried that the Slashdot editors will use your Slashdot password against your Amazon account?

    The idea of Single Sign-On is to put all of your eggs in one basket, then make sure it's a really good basket. Nobody trusts Microsoft to make that really good basket, but it doesn't mean that they're not trying to solve a real problem. It's a tricky one, because the trust factor is scary, and the stakes are very high.

  13. Look for the .NET Passport Sign In button by GillBates0 · · Score: 4, Interesting
    From the .NET Passport page linked to in the blurb, people are supposed to look out for the "button" and when they see it on their site, they can login with their .NET account.

    What's to prevent me from copying their pretty gif and collecting people's logins/passwords?

    --
    An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
  14. MS isn't giving up... by brucmack · · Score: 4, Interesting

    I attended an MS tech talk a couple of months ago about the identity system coming in Longhorn. It seems like they are really targetting mass acceptance with that one too.

    While I can't remember exactly how everything worked (hey, I was there for the food), it was basically an RSA key system, with the private key stored on ones own computer. The main MS involvement was to have some servers set up to allow one to back up their private key so they aren't screwed over if their computer crashes without a backup... and the presenter seemed confident that there would be non-MS providers of the service as well.

    It seemed like a pretty neat idea anyway... There were also systems in place to allow one to deactivate their key if it was compromised. Basically one's computer could notify all of the places it had exchanged its public key with to tell them that it is no longer valid anymore. It seemed like an interesting system that took a lot of the control away from MS, as long as one trusts the OS not to beam the keys back to them :)

    The only real downside was that it seemed like they weren't too keen on getting the server-side software operating on non-MS platforms. But who knows... It certainly seems to be a better solution than Passport, since there would be no fees beyond having a supported OS.

  15. Too expensive by truelight · · Score: 5, Interesting

    Passport has extremely high potential. I tried it out a while back... I went to Slate.com after signing up for a passport, and clicked the "Sign In" button. Now, I had never visited Slate, nor did they have any data on me prior to this. When I clicked "Sign In", that was it. I was registered. No filling out forms. No nothing. From a usability standpoint, Passport has tremendous potential.

    With that said, the fees are absolutely horrendous. I checked it out - $1000/year for "small implementations", and $10000 for other. While I'm all for paying for a good solution, I can't see how having a single-sign-in solution on any website would generate $10000/year in profits.

    I'm sure it would catch on like wildfire if they just lowered the fees to more manageble levels.

    Oh, and buy paypal.

  16. Re:Generic description by ThogScully · · Score: 4, Insightful

    I personally think that it's becoming the groupthink/chic thing to do to point out that the Slashdot crowd doesn't like Microsoft.

    Personally, I'd say the posting of that story should stand as proof that Slashdot isn't so biased as you seem to indicate. Moreover, whenever good news for Microsoft is posted here, it's generally studied with great detail and flaws are exposed in the methodology. For example, in the story you mention, they ignored worms, viruses, trojans, etc, because they didn't involve a person specifically targetting a specific windows machine for an intrusion. I remember thinking that the only valuable thing to come of that study was that Linux/Unix/whatever required actual human intervention to break into it, while Microsoft wasn't worth the bother when a thousand automated tools do it for you.
    -N

    --
    I've nothing to say here...
  17. Re:What's .NET again? by Gr8Apes · · Score: 5, Interesting

    .NET was originally a set of web services, then a service platform, then a server OS, then a set of services on a server OS, then a development platform, and, now, the most known .NET (because I think there's more than one, MS couldn't tell me for sure though) is the multiple language to bytecode platform/compiler.

    Is it any surprise that .NET appears to be fading away? Anything that mucked up by schizophrenic marketing would have to be simply the best thing since the goose that laid gold eggs to survive. And MS's products are definitely not that. (that's not an opinion, see the recent virus outbreak reports for why - just about every major MS product's been hit in the last 6 months)

    --
    The cesspool just got a check and balance.
  18. Re:Problem that doesn't exist big time... by Jerf · · Score: 5, Insightful
    The idea of Single Sign-On is to put all of your eggs in one basket, then make sure it's a really good basket. Nobody trusts Microsoft to make that really good basket, but it doesn't mean that they're not trying to solve a real problem. It's a tricky one, because the trust factor is scary, and the stakes are very high.

    The most recent Cryptogram has a highly relevant comment on this issue:
    [Suppose t]here are 10 $100 piles, each secured by individual $200 security systems. They're all secure. There are another 10 $100 piles, each secured by individual $50 systems. They're all insecure.

    Clearly something must be done.

    One suggestion is to replace all the individual security systems by a single centralized system. The new system is much better than the ones being replaced; it's a $500 system.

    Unfortunately, the new system won't provide more security. Under the old systems, 10 piles of money could be stolen at a cost of $50 per pile; an attacker would realize a total profit of $500. Under the new system, we have 20 $100 piles all secured by a single $500 system. An attacker now has an incentive to break that more-secure system, since he can steal $2000 by spending $500 -- a profit of $1500.

    The problem is centralization. When individual security systems are combined in one centralized system, the incentive to break that new system is generally higher. Even though the centralized system may be harder to break than any of the individual systems, if it is easier to break than ALL of the individual systems, it may result in less security overall.

    There is a security benefit to decentralized security.
  19. Crap can flow uphill by cyberlotnet · · Score: 4, Insightful

    The problem with the whole concept in general to me is security.

    Company A holds your credit card information and controls the sign up system.

    Company B You make purchases through there system, credit card details are pulled from company A, your happy

    Slap on 100 Company B's each with the ability to pull your credit card data so you can make purchases.

    You now have 100 new possible locations for a hacker to crack, giving them access to a massive database of credit card data.

    A chain is only as strong as its weakest link. The more merchants you add to this style system, the better change your chain will break one day.

  20. Passport's Compeitors... by LostCluster · · Score: 5, Interesting

    Passport has gotten a lot of bad press, but there's three other major single signon systems in circulation that nobody talks about...

    AOL's ScreenName Service is used on all Time Warner web properties and partners, including AIM, the Netscape sites, all of the magazines they own and EA's Pogo games site.

    Disney's Go Network may have failed as a portal, but every web domain Disney owns still redirects to a subdomain of go.com such as ABC.go.com and ESPN.go.com. Therefore, there's a full network of news content, e-mail, and a few shopping sites contained there, all of which are Disney-owned properties.

    Yahoo also has a full "network" of sites within the Yahoo.com domain... e-mail, an IM client, games, shopping, and let's not forget there's a serach engine there too. Yahoo lets several partners have your entire account infomation simply by offering a one-click registration into a site such as WorldWinner.com from their games section.

    So, while all the bad press is being aimed at MS... several just as invasive services have quietly gained power.

  21. My "Passport" by oldmildog · · Score: 4, Funny

    For each web site I visit, I have a user ID and then make up a 10 character random password. That's stored in a text file on my laptop which is then encrypted with PGP. When I need to log in to a site, I unencrypt the file, copy/paste the password into the browser, and wipe the file. This is a few more steps than what MS Passport does but is infinitely more valuable to me in making me feel my passwords are relatively secure. BOTH solutions rely on one password to protect all my accounts, but at least in my solution it's a 20-character phrase stored my head instead of one stored in Redmond.

    --
    They have the Internet on computers now?
  22. Apple's Keychain by diamondsw · · Score: 4, Informative

    What works well is Apple's Keychain idea.

    If you want, all of your passwords (web sites, iDisk, e-mail, etc) are all stored in your encrypted keychain on your computer. When you login and authenticate your primary keychain is unlocked, allowing programs that stored passwords to access them. Programs cannot access others' passwords without your consent (in the form of "The application blah wants to access your keychain. Do you want to allow this?"). As would be expected, the whole shebang is encrypted on disk, I believe with AES. Finally, if you don't want all of your passwords in one spot, you can create multiple keychains (e-mail accounts, financial sites, other web sites) and unlock them only as needed.

    It's all local, all secure, very flexible, and by default so easy it's completely transparent.

    --
    I don't know what kind of crack I was on, but I suspect it was decaf.
  23. Passports generate spam by quoll · · Score: 4, Interesting

    Last year we took on a Windows programming contract, so I went ahead and bought an MSDN subscription. In order to log into the online stuff I needed a .Net passport, and this required an email address.

    The address I gave had been around for 3 years and had never received more than a couple of spam messages a week. Within 24 hours of getting the .Net passport that email address was getting over 20 spams a day, and it has grown significantly since then. (Thank goodness it wasn't my primary email account!)

    Conclusion: either the passport user list is being sold, or security is nonexistent. Either way this is not a system anyone sane person would subscribe to!