Chrome's password security insanity can be cured

Prompted by blow-up over Chrome's apathy about password security, expert urges Google to lock passwords with a master key

Google should lock up Chrome passwords with a master key to make casual thieves work harder.

Google should lock up Chrome passwords with a master key to make casual thieves work harder, a security expert said Thursday.

"Google ought to at least be protecting the storage of [Chrome's password] data with a master password," said Andrew Storms, senior director of DevOps at CloudPassage, in an IM interview.

[SLIDESHOW: The worst of 3D printing hype]

Storms was reacting to the blow-up this week after software developer Elliott Kember noticed that Chrome lets anyone with physical access to a computer easily spy and snoop on saved passwords.

Kember called Chrome's practice an "insane password security strategy."

Chrome stores passwords at the user's request, then recalls them automatically for site and service log-ins. A quick trip to the browser's address bar -- type "chrome://settings/passwords" there -- displays accounts, usernames and passwords.

Although the passwords are disguised with asterisks, one click on the "Show" button and the password appears in plain text.

Kember objected to Chrome's system. "There's no master password, no security, not even a prompt that 'these passwords are visible,'" he wrote. Anyone with access to the computer -- a co-worker, say, or a child or spouse on a shared system -- could easily pilfer passwords from the browser. "Today, go up to somebody non-technical. Ask to borrow their computer. Visit chrome://settings/passwords and click 'Show' on a few. See what they have to say," Kember said.

Chrome has always handled passwords this way, but the quick explosion of commentary on the Web signaled that few knew as much.

Google didn't help its case, or Chrome's long-touted reputation as a secure browser, when Jason Shuh, the browser's security tech lead, dismissed the complaints in a message on Hacker News, where he said the password access wasn't an oversight, but by design.

"We don't want to provide users with a false sense of security, and encourage risky behavior," Shuh said to the critics who wondered why Chrome did not, at least, require a second-level password -- a "master key" in the parlance -- to access the in-clear passwords. "We want to be very clear that when you grant someone access to your OS user account, that they can get at everything," Shuh added. "Because in effect, that's really what they get."

Storms didn't see it that way. And from the digital fisticuffs triggered by Shuh's comments, nor did most users.

Shuh was missing the point, said Storms. "Let's agree that one needs access to the computer where the passwords are stored," said Storms. "But they ought to be offering an additional layer of security, a master password, like Firefox does." Otherwise, he continued, there was no barrier to even spontaneous spying.

Google declined to comment on the brouhaha or whether it will react to the online beat down by changing Chrome's password handling.

Click on the 'Show' button in Chrome's saved-password UI and anyone with access to the machine sees the goods.

Chrome isn't the only browser than lets anyone with access to the machine see passwords: Mozilla's Firefox does too, although as Storms noted, it does offer an option of locking access with a second, or master, password.

Apple's Safari and Microsoft's Internet Explorer (IE) are more secure from ad hock password theft. Both require users to again enter their user account password -- the operating system's overarching log-in password -- to view saved passwords, in effect treating the user account password as a master key.

All four browsers encrypt the password file, some using stronger encryption than others. But Chrome and Firefox automatically call on the existing user account password to decrypt the file without asking the person in front of the key to lift a finger.

Put plainly, the casual thief who steps up to the keyboard of a running PC or Mac has to also know the user account password to view Safari's and IE's password file. But they can immediately see its contents on Chrome, as well as on Firefox if no master key has been set earlier.

Thus, Storms' call for Google to add an optional master password to Chrome so that it's at least on par with Firefox. Requiring people to type in the user account password once again would be even better.

This week's Chrome password crisis was not news: The issue has come up before, although the blow-back this time has been staggering in comparison. "That was my first reaction, actually," said Storms when asked whether the new brouhaha is a tempest in a teacup, or is legitimate. "It's been like that for a long time ... [so] why now and doesn't everyone already know this?"

But Storms wasn't downplaying the concern of critics. "It is a rather strange situation, since Chrome drove to the top of the list [based on it being] the most secure browser from online malware," he said.

Inserting a master key requirement into Chrome should not be a big deal, code-wide, Storms said. "I wouldn't think it would be that difficult for them," he said.

Users reluctant to let Chrome or any other browser save passwords have options, Storms said, notably password managers that are specifically designed to secure passwords while still making them readily available for site log-ins.

Storms suggested 1Password (Windows, OS X; $49.99). But there are lots of other choices, including KeePass (Windows; free), LastPass (Windows, OS X; free or $12/year for premium version) and RoboForm (Windows, OS X; $29.95).

Gregg Keizer covers Microsoft, security issues, Apple, Web browsers and general technology breaking news for Computerworld. Follow Gregg on Twitter at @gkeizer, on Google+ or subscribe to Gregg's RSS feed. His email address is gkeizer@computerworld.com.

See more by Gregg Keizer on Computerworld.com.

Read more about internet in Computerworld's Internet Topic Center.

This story, "Chrome's password security insanity can be cured" was originally published by Computerworld .

Editors' Picks
Join the discussion
Be the first to comment on this article. Our Commenting Policies