Live data from Hacker News

How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

raidersec.blogspot.in

61–70 of 82 posts

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#61
post #43

Earlier quoted context omitted.

Laptops.

Show me a new laptop that isn't a netbook that is lower than 1024px wide. This guy is living in '99 designing solely for 800px wide screens.

I'm not super informed on web-design trends, but I think fixed-width designs are still pretty common. They work. Why do you think you can discount netbooks, anyway?

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#62
post #25

One thing I've been meaning to test. Does Chrome's form-autofill (the thing where it fills in as much of a form as it can when you specify an email address) populate hidden fields if they match? If-so, it seems like potential for mischief to create some form inputs of type "hidden" or just some visually-hidden form inputs using style sheets to capture more information than a user is aware is being populated and submi…

No. Why would it do that.

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#63
post #42
post #40

Earlier quoted context omitted.

This is a failure of the browser manufacturers, not the users. I had no idea this was even possible until now- they should surface a feature like this a lot more clearly if they want people to use it.

And yet users have repeatedly flocked to software, including browsers, that "surface" less features.

There is a middle-ground. Something like MS Office's 'Ribbon UI' where they set out to minimize the interface while exposing features that were usually hidden deeply enough that users couldn't find them.

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#64
post #30

Earlier quoted context omitted.

Like I said, I opt to use 1Password instead for cross platform usage.

So locally running malware only needs to keylog your master 1Password password to decrypt your 1Password data file?

If you have a keylogger on your machine, all hope is lost. This is true for any password based security, much like a the best safe in the world is thwarted by someone videotaping you entering the combination. Even so, 1Password does utilize sandboxing in OS X and a secure desktop in Windows, which should in theory make this significantly harder to achieve.

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#65
post #30

Earlier quoted context omitted.

So locally running malware only needs to keylog your master 1Password password to decrypt your 1Password data file?

If you have a keylogger on your machine, all hope is lost. This is true for any password based security, much like a the best safe in the world is thwarted by someone videotaping you entering the combination. Even so, 1Password does utilize sandboxing in OS X and a secure desktop in Windows, which should in theory make this significantly harder to achieve.

Yes... and the premise of the original post was about vulnerability to arbitrary code being executed on the machine with the user account's rights. I.e., nothing's stopping the keyloggers now.

This is the airtight hatchway we're talking about. The post's premise, and the solutions for Chrome and IE, imply bad guys are already on the other side. All hope is lost. Best you can do is try and make it so that anyone just stumbling around rather than purposefully looking for the passwords doesn't find them, and the value of that is questionable on false sense of security arguments.

It's non-news to anyone who understands how Windows is built.

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#66
post #45

Chrome OSX stores in OSX keychain, out of the box. Which is a fairly secure way to store passwords.

The Linux version does the same with KWallet or the Gnome keychain, as long as you're using KDE or Gnome.

Gnome-keyring doesn't have many dependencies, so you can run it with any desktop environment or window manager. Recent versions of Xfce have built-in support for loading it at login. It also integrates nicely with GPG, SSH, and network-manager. I'm not sure about KWallet.

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#67
post #33

Also in Chrome: Go to Settings -> Show advanced settings -> Manage saved passwords -> Click on a "hidden" password -> Click on "Show" button -> Voila, password shown in plain text

Absolutely! This functionality is present in most (if not all) browsers. The goal of this post was to show how malware could automatically attempt to extract all credentials. However, that's certainly a good feature to mention!

But passwords are already available in plaintext. This fact alone means that passwords are not exactly hidden from the logged in user.

As an analogy, say you have a house and you have a drawer where you keep all your secret information. If you really want to keep the information secret, then you shouldn't allow outside visitors inside your house. You could encrypt the secret information to make it difficult for the attacker to read the information. But he still has access to your drawer because you let him into your house. The attacker can install a remote camera near your drawer to see how you decrypt the information, or he can directly see the decrypted plaintext.

So, don't allow anyone into you house.

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#68

Earlier quoted context omitted.

Why, that's almost as easy as remembering the new number to dial emergency services! http://www.youtube.com/watch?v=ab8GtuPdrUQ

How about I put it this way: "All you have to do is go to password settings and click the button" And you only have to go there once ever. I think it's usually assumed users can navigate menus, because even if they can't there's not much you can do to help them at this point.

Users can navigate menus. But given the out-of-the-way location of the "Use a master password" checkbox, what percentage of Firefox's users even know of it's existence? It's likely pretty low.

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#69
post #48
post #34

Earlier quoted context omitted.

Hi there! Sorry about the resolution issue.. I'm using Google's blogspot with settings not adjusted too much (only widened a few things, etc.) Any suggestions as to what I could do to help you read the content?

Thanks for your reply. The situation is very common on the Web now. My 17" monitor is from NEC years ago, is razor sharp and rock solid, and I see no great reason to take time out to change from it. Besides, as another comment in this thread noted, laptops also have relatively small screens! So do tablets and phones! I know nothing about using Google's blogspot. For the Web site I'm building, all screens are just 800…

Your web pages with fixed width of 800px may be fairly annoying to users with high-DPI displays. Mac Retina displays are perhaps the most recent and well known, but for years some people have had displays with DPI 50-200% higher than "normal", and for these people, your 800px decision looks like handcuffs. If you look back a dozen years you'll see a number of sites that instituted fixed-pixel-width layouts, then abandoned the approach as people bought more large, high-res displays.

P.S.: Yes, some operating systems and browsers now zoom in a way that this doesn't matter so much, but not all, and not without downsides.

Re: How Browsers Store Your Passwords (and Why You Shouldn't Let Them)

#70
I don't get it, if there is malware on your computer you are compromised anyway - it could just keylog to get the passwords... so why bother about how secure is to get the stored passwords for a program running on the same computer?

...if there was a remotely exploitable browser bug that would make the browser leak them it would be a threat, but this post seems meaningless from a security pov.

Post reply on HN