News for hackers. Stuff that matters.
Re:Introducing BrowserID: A better way to sign in by JoshTriplett on Thursday July 14, 2011 @06:44PM (#2765492)
Why would you want your email provider to support BrowserID? I'd consider it invasive for my email provider to do anything different to interfere with the email verification process for another site.
Re:Introducing BrowserID: A better way to sign in by bct on Thursday July 14, 2011 @06:48PM (#2765500)
I don't follow you, what's invasive/interfering about it? You & your browser can decide whether any of the steps of this process actually happen.
Re:Introducing BrowserID: A better way to sign in by JoshTriplett on Thursday July 14, 2011 @07:05PM (#2765561)
The proposed BrowserID standard specifically suggests that the browser should ask the email provider to validate the email, and only fall back to the usual email-me-a-link validation if the email provider doesn't "natively" support BrowserID. I'd prefer to always go through email-me-a-link verification (ideally with some kind of crypto involved), rather than involving the email provider in any way other than SMTP and IMAP.
Re:Introducing BrowserID: A better way to sign in by bct on Thursday July 14, 2011 @07:16PM (#2765594)
Can you link me to where you're reading that? I don't see anything like that (but I've only skimmed the documentation).
Re:Introducing BrowserID: A better way to sign in by JoshTriplett on Thursday July 14, 2011 @07:48PM (#2765676)
See the teaser at https://browserid.org/primaries , and the documentation at http://lloyd.io/how-browserid-works .
Re:Introducing BrowserID: A better way to sign in by bct on Thursday July 14, 2011 @09:28PM (#2765927)
I've read it more thoroughly now, but I'm still not sure where you're coming from. You'd rather use a secondary identity authority, even when a primary is available? Or are you saying you'd like to require a full send-me-an-email-and-i'll-click-on-a-link verification every time you log in to a relying party?