5 ms·
The centralized persona.org service seemed like the weakest link in an otherwise interesting distributed authentication system; persona.org gave people a "trans
by JoshTriplett 11y ago
The centralized persona.org service seemed like the weakest link in an otherwise interesting distributed authentication system; persona.org gave people a "transitional" way to associate logins with email addresses rather than federated IDs, but as far as I can tell, nobody ever used anything else. It makes me sad that Mozilla never followed through with the browser integration component of BrowserID.
Consider this for a browser-integrated login system:
- Browsers directly provide an API for sites to say they need to say "this site wants an account".
- When the browser sees such a request from an origin that the user doesn't have an account for, it provides browser UI to create an account and log in. Creating an account creates an origin-specific keypair in the browser and hands the site the public key; logging in uses a challenge-response protocol to prove ownership of the private key.
- When the browser sees such a request from a site the user has an account for, it provides browser UI to log in via the challenge-response protocol; that same browser UI can offer options like "keep me logged in".
- Both Firefox and Chrome have cross-system synchronization systems (e.g. Firefox Accounts/Sync), including to mobile browsers. Use those systems to sync the keypair across browsers controlled by the same user. Perhaps offer options to copy individual keypairs via QR code or similar, for the much smaller set of people who have systems of varying trust levels that should each have access to overlapping subsets of accounts.
- The browser can (at the user's option) provide an email address to a site. The site can (at the site's option) provide an option to register a new key for that email address, as the equivalent of a "lost my password" system but for "lost my computer or browser profile".
This implementation seems quite straightforward. About the only problem I know of that it doesn't solve involves throwaway accounts with memorized passwords used only with private browsing, where people don't want to leave a trace. If people care enough about that case, perhaps offer the option (such as when using private browsing) to compute a key from the origin, the user's email address, and an optional password, and throw it away at the end of the session. (For that matter, browsers could generate a completely transient key, for those times when you want to make a throwaway account that you'll never want access to again unless the site has an email-based recovery option.)
While this system provides some useful properties for highly technical users, it seems quite feasible to present it in an extremely simple manner for novice users.
- XMPPwocky 11y agoUAF, from the folks behind U2F, does basically this: https://www.ietf.org/proceedings/92/slides/slides-92-tokbind-3.pdf https://www.ietf.org/proceedings/92/slides/slides-92-tokbind... As far as usability, at least U2F is amazingly frictionless; enrollment is 'put the dongle in and hit the button', login is 'put the dongle in and hit the button.'
- zeisss 11y agoIs it nowadays supported by more than Chrome?
- XMPPwocky 11y agoU2F or UAF? Firefox is working on adding U2F support, and there's a third-party plugin ( https://addons.mozilla.org/en-GB/firefox/addon/u2f-support-add-on https://addons.mozilla.org/en-GB/firefox/addon/u2f-support-a... ). Not sure if anything supports UAF yet; doesn't seem to have the same momentum as U2F.