Identifier recycling is also an issue with phone numbers. There are a number of two factor mechanisms (and primary mechanisms) that rely on the user being bound to their phone number.
Personally, I think dealing with identifier recycling is low in the list of issues. A huge plus for email is that it is a non-propritary identifier that almost everyone on the internet has, and that you have for many of your contacts. A critical component of sharing. Facebook is viewing sharing as the important growth metric, and if OpenID has any hope of cracking the Facebook identity juggernaut, being able to identify who you want to share with is critical. As for one of the major advantages of BrowserID: it is a user-centric architecture unlike OpenID Connect. -- Dick On 2011-07-19, at 12:39 AM, Nat Sakimura wrote: > Relying party using somebody's email address as login name and site specific > password was screwed today as you say. > We should fix the problem. > > Email providers can actually distinguish between the old user and new user, > and password reset by email does not cross the old and new accounts so they > are not plagued by this problem. They should help the situation. One idea for > BrowserID is for the email provider to issue a certificate that includes a > canonical identifier of the user. Then, relying parties can use that as the > identifier and email as an attribute. In OpenID term, email is the user > supplied identifier and the unique string is the canonical identifier. > > =nat > > On Tue, Jul 19, 2011 at 2:14 PM, Allen Tom <[email protected]> wrote: > Email address recycling is an important issue, but since the status quo > (password reset via email) doesn't address the recycling issue, perhaps it's > not necessary to solve it. > > It is important that RPs allow users to change their email address to prevent > their RP account from being taken over if they lose the email address that > they used to create the account. Perhaps that's good enough? > > Allen > > > On Mon, Jul 18, 2011 at 10:02 PM, Nat Sakimura <[email protected]> wrote: > One of my concern around BrowserID is that it does not seem to take care of > the email address recycling. > Email address verification "certificate" may be short lived but it does not > solve the impersonation problem at all. > There has to be some ways of canonicalizing email address into a > non-re-assignable identifier. > Otherwise we are screwed and BrowserID spec does not yet provide the > solution. > > As a conceptual solution, BrowserID is interesting if the browsers implements > it and if we can get rid of BrowserID.org. > I would like to see more work towards. it. > > =nat > > On Tue, Jul 19, 2011 at 1:05 PM, Allen Tom <[email protected]> wrote: > Yeah, I totally agree - I was referring to a hypothetical protocol that's > similar to OpenID Connect, but uses email addresses as the true identifier. > > I don't see how BrowserID would be better than a version of OpenID Connect > that only uses email addresses as the one true identifier. > > Allen > > > > On Mon, Jul 18, 2011 at 8:51 PM, Phillip Hallam-Baker <[email protected]> > wrote: > There is an advantage to throwing out the bad identifiers, It allows the user > interface to be made a lot simpler as anything not an email address is wrong. > > No URLs, no XRIs. > > > As for what to do if the email provider does not provide BrowserID, I don't > think it is a problem, I would probably separate the accounts in any case. > > > _______________________________________________ > specs mailing list > [email protected] > http://lists.openid.net/mailman/listinfo/openid-specs > > > > > -- > Nat Sakimura (=nat) > Chairman, OpenID Foundation > http://nat.sakimura.org/ > @_nat_en > > > > > > -- > Nat Sakimura (=nat) > Chairman, OpenID Foundation > http://nat.sakimura.org/ > @_nat_en > > _______________________________________________ > specs mailing list > [email protected] > http://lists.openid.net/mailman/listinfo/openid-specs
_______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
