Mozilla Proposes Master Password System

BrowserID aspires to solve the problems posed by passwords, even if OpenID is already on the case.

Mozilla's Webian Shell: A Web-Only Operating System Layer
Slideshow: Mozilla's Web-Only Operating System
(click image for larger view and for slideshow)
Mozilla on Thursday introduced BrowserID, a system for signing in to different websites using a single email address as a common account identity.

BrowserID aims to relieve users of the burden of maintaining different user IDs and passwords for every site. Of course, not everyone bears this burden: Many users disregard security advice and maintain identical or similar account names and passwords across different websites.


More Internet Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

BrowserID could also help developers by alleviating the need to implement email verification and by allowing developers' sites to provide a better user experience.

The way the system is supposed to work is simple for the end user: Click a sign-in icon at a BrowserID-compliant site, get redirected to the BrowserID site, enter one's email address and a new master password, receive a verification email, and click on the verification link. Thereafter, clicking a sign-in icon at any BrowserID-compliant site allows the user to login using his or her verified email address, simply by selecting the address from a menu.

On a technical level, BrowserID is a cryptographic scheme to prove email account ownership to a given website.

While major web companies may prefer that users accept their login and identity systems, Mozilla's Dan Mills suggests users are better off trusting an open-source, community-focused organization.

"Outsourcing login and identity management to large providers like Facebook, Twitter, or Google is an option, but these products also come with lock-in, reliability issues, and data privacy concerns," he said in a blog post.

OpenID, a decentralized authentication system supported by AOL, Google, IBM, PayPal, and Yahoo, among others, was meant to provide just such a non-proprietary alternative. But Mozilla argues that OpenID falls short.

"What we've learned from several years of experience with OpenID (and related protocols) is that this isn't quite good enough: establishing an identity token, in isolation from the rest of the web, doesn't actually help a site engage with its users," the company says on its website.

Mozilla acknowledges that its system requires further work before it is secure. For example, the company's documentation notes that a mail host administrator could take control of users' email accounts, a risk for any system but one of particular concern if one's email address becomes a means of authentication across the web.

The problem however goes beyond ill-intentioned administrators: Establishing a system that makes email accounts the keys to every website would only increase efforts by malicious hackers to take over email accounts. Law enforcement authorities might also recognize the value of a key that opens every locked account associated with a given user.

But BrowserID also has advantages beyond ease of use and deployment: It has been implemented entirely in HTML and JavaScript and it doesn't leak information back to any server about the sites a user visits.

Mozilla is encouraging interested parties to visit the BrowserID website to try the system out and perhaps contribute code to improve it.

Black Hat USA 2011 presents a unique opportunity for members of the security industry to gather and discuss the latest in cutting-edge research. It happens July 30-Aug. 4 in Las Vegas. Find out more and register.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links