News for hackers. Stuff that matters.
Re:Introducing BrowserID: A better way to sign in by JoshTriplett on Thursday July 14, 2011 @07:02PM (#2765550)
That site fails terribly at supporting OpenID: it only supports four authentication providers, and doesn't allow a user to enter an arbitrary OpenID URL.

"Properly implemented", OpenID looks like http://ikiwiki.info/ikiwiki.cgi?page=index&do=edit : a choice of common OpenID providers to help users who don't understand OpenID, an option to use an arbitrary OpenID, and an option to use a username and password.

Properly implemented, BrowserID looks like one big shiny "sign in" button, and yet it still supports any service the user wants to use, and better yet no third-party service at all. Seems like a big improvement to me.

Re:Introducing BrowserID: A better way to sign in by nolliesnom on Friday July 15, 2011 @10:59PM (#2769990)
There are legitimate reasons to whitelist OpenID providers, especially if you are dealing with $$ or want to minimize support costs.
Re:Introducing BrowserID: A better way to sign in by jancona on Friday July 15, 2011 @12:20PM (#2767984)
Why do you think a "properly implemented" OpenID site should allow the user to use any authentication provider? The relying party site is trusting the OpenID provider to authenticate its users. Wouldn't sites with real security requirements want to vet providers before trusting them?
Re:Introducing BrowserID: A better way to sign in by js4all on Friday July 15, 2011 @03:02PM (#2768619)
Exactly right.

And all OpenID providers have different attribute exchange protocol extensions. If you use them, you can effectively allow only those you have tested.