This seems to encourage using the same credentials everywhere which I think most agree is a "bad idea." If BrowserID is compromised, the attackers have access to all the sites where I use browser id, right?
Introducing BrowserID: A better way to sign in
31–40 of 188 posts
Re: Introducing BrowserID: A better way to sign in
#32Re: Introducing BrowserID: A better way to sign in
#33Re: Introducing BrowserID: A better way to sign in
#34I should be able to change my email address (and/or email hosting provider) without changing my identity on a bazillion sites around the internet. Facebook got this right from the beginning. Google is sort-of getting this, although the chasm between Google Accounts and Google Apps Accounts makes this really messy.
Really this product should be called BrowserEmailAddress, not BrowserID. It doesn't serve identity.
Re: Introducing BrowserID: A better way to sign in
#35Re: Introducing BrowserID: A better way to sign in
#36Earlier quoted context omitted.
It actually is decentralized, in the sense that anyone can implement a BrowserID provider.
Anyone can , but from the looks of it, a site chooses to trust one at a time.
1. Primary Identity Authority. This is a host (i.e. the one in your email address) that supports BrowserId. This is fully decentralized.
2. Implementation Provider/Secondary Identity Authority. For now the site has to choose one to trust, but once your browser has support it becomes the IP, and when your host becames a PIA there's no need for an SIA.
Re: Introducing BrowserID: A better way to sign in
#37One huge problem: Email address != identity. I should be able to change my email address (and/or email hosting provider) without changing my identity on a bazillion sites around the internet. Facebook got this right from the beginning. Google is sort-of getting this, although the chasm between Google Accounts and Google Apps Accounts makes this really messy. Really this product should be called BrowserEmailAddress, n…
It's very similar to the countless existing services that rely on email for identity... you'd just have to verify ownership of the new email address (usually through a confirmation email).
Re: Introducing BrowserID: A better way to sign in
#38What I'd really want to see is public-key authentication for website. Let me upload my public key when I create an account on a website, and let the browser interact with my ssh-agent to authenticate.
http://www.gnegg.ch/2008/05/why-is-nobody-using-ssl-client-c...
Re: Introducing BrowserID: A better way to sign in
#39Re: Introducing BrowserID: A better way to sign in
#40How is it different from OpenID, apart from it's not decentralized?
This lets users sign in with an existing email address, so they don't need any new sevice or identifier to remember. It's decentralized; Mozilla has a service for web developers for convenience, but any site can implement the protocol itself instead (or use another provider). And it's designed to let browsers handle the login flow in the future, simplifying login and account creation for end-users.
Literally the same thing, here.