Live data from Hacker News

The war against autocomplete=off (2013)

blog.0xbadc0de.be

51–60 of 78 posts

Re: The war against autocomplete=off (2013)

#51
post #36

I just use this bookmarklet to remove "autocomplete=off" from form elements: javascript:(function(){var%20c=0;function%20R(w){try{var%20a,df,dfe,i,j,x,y,r=1;df=w.document.forms;for(i=0;x=df[i];++i){dfe=x.elements;if(a=x.onsubmit){a=""}if(a=x.attributes["autocomplete"]){if(a.value=="on"){c++}a.value="on"}for(j=0;y=dfe[j];++j){if(a=y.attributes["autocomplete"]){if(a.value=="on"){c++}a.value="on"}}}}catch(E){r=0}return%…

There’s also the Chrome extension autocomplete=on from a Chromium author: https://chrome.google.com/webstore/detail/autocomplete-on/ec...

Shameless plug:

I dot so worked up over this kind of nonsense one day that I wrote a firefox addon to turn autocomplete on. https://addons.mozilla.org/En-us/firefox/addon/autocompletea...

Re: The war against autocomplete=off (2013)

#52
post #14

The original article fails to take into account the larger population. The basic password managers in browsers are huge security holes. The one in FF does not use a master password by default, so anyone could look at an unattended computer and see all stored passwords with a few clicks. The article mentions an old JavaScript attack on the passwords as well (but then dismisses the threat, since that one hole was patch…

You might not agree with this but hear me out. I used to work on Chrome and I was curious what the justification was for storing passwords unencrypted in Chrome. I went and talked to the Chrome security team and they frustratingly explained it to me as they get this question all the time.

As you said, in FF, (and in Chrome), a few clicks and anyone could look and an unattended computer and see all the stored passwords. As they pointed out, an unlocked unintended computer can pretty much be owned by anyone who wants to own it. You've given them access to your computer. They can open a shell and start running apps. They can exploit any bug in the OS or other app. They can copy files to a USB stick or across the net. On top of that, your password manager (or FF or Chrome) will let them log into your mail, your bank, your facebook, whatever services you've saved passwords for even without knowing your password.

The point is

(1) don't leave your computer unlocked and unattended. Put a password on it, when you walk away from the computer lock the computer (start the screensaver or whatever that makes it required you to use a password to get back in)

(2) don't ever let someone use your computer logged in as you. If you hand someone your computer to use login as guest then hand it to them.

If you're like me you'll probably reject these suggestions. I thought "I don't want to be bother to lock and unlock my computer all the time" and I thought "It's stupid to expect me to put my computer in guest mode anytime I let someone else use it."

But, after I calmed down and thought about it I realized they are right. If someone wants your passwords or other data and you hand them an unlocked machine they are going to get them. How FF or Chrome or Password managers store passwords has nothing to do with that.

Re: The war against autocomplete=off (2013)

#53
I'm going to go with Bruce Schneier on this one and say that there is absolutely nothing wrong with writing your passwords down. If someone mugs me and takes my wallet there is a 99% chance they are going to get the phone too and I'll need to change all my passwords anyway.

Not letting the browser cache them is still dumb though.

Re: The war against autocomplete=off (2013)

#54

The first thing I install in a new browser is an adblocker. The second thing an addon that disables autocomplete=off. Yes I'm lazy. But my laptop is encrypted and goes back to the login screen after 2 minutes of inactivity. To me autocomplete=off is just annoying and doesn't add any security.

it really helps with forms where you are an admin and can edit other users information... in these forms when autocomplete is on... and starts populating your information into the user you're trying to edit... well... things just get pretty messed up...

Re: The war against autocomplete=off (2013)

#55

The first thing I install in a new browser is an adblocker. The second thing an addon that disables autocomplete=off. Yes I'm lazy. But my laptop is encrypted and goes back to the login screen after 2 minutes of inactivity. To me autocomplete=off is just annoying and doesn't add any security.

I used to be annoyed by autocomplete=off until I started using 1Password. Now, I actually tell Chrome to disable auto-filling of forms since I can fill the form fields with 1Password, which is the only place I'm keen to store personal information.

Re: The war against autocomplete=off (2013)

#56
post #47
post #3

I've run into the problem of web services not letting me store passwords. The reality is, if you let my password manager (safari jacks into OS X's keychain system) keep track of things, I'm going to use the random 12-digit alphanumeric password my password manager provides me. If you don't, I'm either going to use my shitty "brain" password or put it in my password manager anyway and just copy-paste it manually. Than…

http://xkcd.com/936

A random 12-digit alphanumeric is log((26+26+10)^12)/log(2) = 71.45 bits of entropy. Plenty for a web form.

Re: The war against autocomplete=off (2013)

#57

> Tell me how I am supposed to fulfill these requirements if I need 20 websites daily to do my work ? One solution to this problem (or at least one way to severely mitigate it) is to use a base word that you tweak with a simple algorithm based on the first letter, last letter, number of letters in the domain, etc. Of course some websites have mutually exclusive requirements, so this doesn't work for all sites, but I'…

I changed all my passwords recently to do the same thing. The problem I've recently started to see is that, let's say for example my hashed+salted password is stolen from a site. If they brute-force figure out what my password is, they'll have my "base word" and all my other accounts may still be able to be compromised. Recently I changed my big accounts (Google, Facebook, StackOverflow) to have a slightly different…

It's significantly more difficult to reuse the base and figure out the additional characters than it is to get access to the user whose password is 'password'

For insecure services that I use on mobile, public, etc computers, I do this.

Post reply on HN