Re:Introducing BrowserID: A better way to sign in
by starwed on Thursday July 14, 2011 @09:47PM
(#2765975)
Did you read the article? This is an attempt to fix all those issues you list.
Re:Introducing BrowserID: A better way to sign in
by kpanghmc on Friday July 15, 2011 @12:31AM
(#2766284)
BrowserID only fixes those issues if it ends up as the only game in town. Otherwise, it's simply going to be tacked onto the end of a daunting list of other OpenID / BrowserID providers that users will have to choose from.
Re:Introducing BrowserID: A better way to sign in
by speckledjim on Friday July 15, 2011 @04:29AM
(#2766682)
So now when your email address gets hacked, ALL your usernames and passwords to every website are also hacked!
At least with normal un/pw you need to request a password reset from the website.
I don't think we should be tying logins to email.
Re:Introducing BrowserID: A better way to sign in
by 21echoes on Saturday July 16, 2011 @03:40AM
(#2770353)
by tying all your logins to email, you're left with only one account that you can focus on keeping secure and un-hacked (or a few, as BrowserID allows for multiple emails). The BrowserID is also in talks about support one-off identity generation via the browser, bypassing email on sites which you don't want to identify with.
BrowserID supports password reset requests, which can be built into the browser
email is the single most user-recognized signifier of identity we have on the internet today. tying identity to anything other than email just seems silly
Re:Introducing BrowserID: A better way to sign in
by ora600 on Thursday July 14, 2011 @09:44PM
(#2765971)
You see, passwords suck. Big time. They are extremely vulnerable to brute-force attacks, people forget them, people write them down on post-it notes, and people use the same password on every single site. Not to mention that the website has to store your password securely, and not every website has amazing track record doing that.
Passwords make the world less secure.
So we need to replace them with something. And that "something" has to be secure and easy to use.
Turns out that this is a difficult problem to solve, so we keep trying. I agree that OpenID is not exactly the perfect solution, but it doesn't mean that there is no problem to solve.
Re:Introducing BrowserID: A better way to sign in
by kpanghmc on Friday July 15, 2011 @12:35AM
(#2766290)
I never said that there wasn't a problem. I'm simply saying that the solutions we've come up with so far have not yielded a net gain. If anything, the site owners that I know who have incorporated OpenID / Facebook Connect / etc. into their sign up / login forms have said that they have to answer more questions from users having login issues than ever before.
Re:Introducing BrowserID: A better way to sign in
by snorkel on Friday July 15, 2011 @12:23PM
(#2767997)
I like this approach specifically because it doesn't have to replace the traditional sign-in process. A BrowserID sign-in button can be added to a traditional sign-in form without any fuss, and users can either use it or ignore it. And if the BrowserID sign-in is broken, then no worries, the traditional sign-in form works anyway.
Now, instead of simply having to remember what username/password combination I used, I have to remember which (if any) OpenID provider I used, how much information about myself does said provider expose, and how to merge my accounts when I inevitably end up choosing the wrong provider and create a duplicate account on the site.