Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

9/27/2012
04:23 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Mozilla Persona Aspires To Kill Passwords

Mozilla system promises Web authentication without site-specific passwords. User's browser will generate a cryptographic 'identity assertion' that expires after a few minutes.

11 Security Sights Seen Only At Black Hat
11 Security Sights Seen Only At Black Hat
(click image for larger view and for slideshow)
The password is dead, again.

Mozilla on Thursday said that its Persona Web authentication system, which eliminates the need to enter site-specific passwords at participating websites, has entered its beta phase and is ready for general deployment.

Passwords should have died long ago. No less than Microsoft chairman Bill Gates declared them dead in 2004. But as a Microsoft researcher noted last year, passwords still have a pulse.

"Despite countless attempts to dislodge them, passwords are more widely used and firmly entrenched than ever," said Cormac Herley, principal researcher in the machine learning department at Microsoft Research, and Paul C. van Oorschot, professor of computer science at Canada's Carleton University, in a research paper.

Were passwords to die, online security might improve. That's the theory anyway, if you assume that there's nowhere to go but up, that cybercriminals won't adapt, and that technology rather than humanity represents the weakest link in the chain. At the very least, the end of passwords would eliminate the possibility of having your password posted on pastebin.com following a data breach and having to explain to friends and colleagues why choosing "password" as your password seemed like a good idea at the time.

[ Read Google Autonomous Cars Get Green Light In California. ]

Like other single sign-on systems--and there are many--Persona promises to allow third-party websites to authenticate users without requiring them to ask for usernames and passwords.

"Instead of per-site passwords, Persona lets users log into sites with just two clicks after completing a simple, one-time process for each of their identities," Mozilla explains on its website. "This is safe, secure, and built on top of public key cryptography. Instead of a password, the user's browser generates a cryptographic 'identity assertion' that expires after a few minutes and is only valid on a single site."

Persona, says Mozilla, is easier to use than OpenID, another authentication system, because it is based on the user's email address rather than a URL generated by OpenID.

Email addresses have two distinct advantages. First, they're pseudonymous and thus provide more privacy than single sign-on systems used by Facebook and Google+, which require the use of real names. Second, they're subject to greater user control: Individuals can register and operate their own Internet domain, to more or less own their email identity. At services such as Gmail or Yahoo Mail, users cannot take their email address to another service provider if they're dissatisfied.

Persona's architecture also provides a privacy advantage. Whereas systems like OpenID require third-party websites to contact an authentication provider, Persona makes the user's browser the intermediary, passing credentials from the email provider to the third-party website. This exposes less website visit data to potential tracking.

There are benefits for businesses that adopt Persona, too. Mozilla's system provides developers with access to email addresses, enabling websites and app makers to contact their customers and eliminate the friction of soliciting an email address separately. Email addresses also play nicely with most existing login systems.

The problem with authentication systems is business buy-in. Online content and service providers might choose to integrate an authentication system like Persona, but they have tended to avoid doing so. A 2010 study conducted by the University of British Columbia's Laboratory for Education and Research in Secure Systems Engineering on the failure of single sign-on technology, A Billion Keys, but Few Locks: The Crisis of Web Single Sign-On, found that the among websites that could implement OpenID, the adoption rate was less than 0.02%.

The paper cites a number of reasons for disinterest in the technology: lack of business incentives, competitive concerns, usability, security, privacy, trust, and legal issues. The lack of business incentives for becoming a "relaying party"--that is, integrating an external authentication system--appears to be the biggest impediment to making single sign-on systems more appealing.

Although adopting a technology like Persona might have operational benefits, such as reducing password maintenance and recovery costs, doing so often doesn't have competitive benefits. Indeed, relying on an external authentication system might impose a competitive disadvantage if it deprives a company of potentially valuable user data or makes the company dependent on a potential competitor. The paper characterizes the situation as an "identity war" that "has been ongoing since the beginning of the Web" to build walls to keep customers and competitors apart. Imagine Google allowing users to sign in using a Facebook ID or vice versa and the problem becomes clearer.

However, Persona's association with Mozilla, a non-profit organization, might work to its advantage. Companies that might have balked at becoming reliant on a platform-based authentication system from the likes of hyper-competitive Facebook or Google could be more willing to trust Mozilla and its open Web ethos.

IDC analyst Sally Hudson characterized the issue as a balance among cost, convenience, and risk. "Consumers (or even corporate employees) will try to bypass or avoid using complex authentication mechanisms," she said in an email. "In a world where revenues are often driven by eyeballs and mouse clicks, anything that annoys or slows the consumer down in their quest to purchase a product or apply for a service is quickly discarded."

However, she cautioned, while anything is better than nothing when it comes to authentication, "there is no foolproof authentication method or standard on the market today."

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...