If you use passwords, there’s a good chance you’re doing them wrong and exposing yourself to unnecessary risk.
My intent is provide some basic information on how you can do passwords better1, suitable for grandma to use (no offense grandma), because there’s no reason that you can’t do passwords better.
Why We Have Passwords
In the beginning, the internet was a benevolent place. If I said I was fergbrain, everyone knew I was fergbrain. I didn’t need to prove I was fergbrain. Of course, that didn’t last long and so passwords were created to validate that I was, in fact, fergbrain.
Passwords are one of three ways in which someone can authenticate who they are:
- Password: something you know
- Token: something you have that can’t be duplicated (such as an RSA token or YubiKey)
- Biometric: something you are (such as a fingerprint or other biometric marker unique to you)
Back In The Day™, passwords were the de facto method of authentication because they were the easiest to implement and in many ways still are.
At the time, token-based methods were just on the verge of development with many of the technologies (such as public-key encryption) not even possible until the mid 1970’s. And once suitable encryption was more completely developed2, it could not be legally deployed outside of the United States until 1996 (President Clinton signed Executive Order 13026).
Finally, biometric authentication was an expensive pipe dream3.
The point being: passwords where the method of choice; and as we know, it is quite difficult to change the path of something once it gets moving.
Having just one password is easy enough, especially if you use it often enough. But how many places do you need to use a password? Email, social media, work, banking, games, utilities…the list goes on.
It would be pretty hard to remember all those different passwords. So we do the only thing we believe is reasonable: we use the same password. Or maybe a couple of different passwords: one for bank stuff, another for social media, maybe a third one for email.
Why Passwords Can Be a Problem
Bad guys know that most people use the same username, email address, and password for multiple services. This creates a massive incentive for bad guys to try and get that information. If the bad guys can extract your information from one web site, it’s likely they can use your hacked data to get into your account at other web sites.
For bad guys, the most bang for the buck comes from attacking systems that store lots of usernames and passwords. And this is how things have gone. Over just the last two years Kickstarter, Adobe, LinkedIn, eHarmony, Zappos.com, last.fm, LivingSocial, and Yahoo have all been hacked and had passwords compromised. And those are just the big companies.
In my opinion, most people know they have bad passwords, but don’t know what to do about it. It’s likely your IT person at work4 keeps telling you to make “more complex” passwords, but what does that mean? Does it even help? What are we to do about this? Can we do anything to keep ourselves safer?
How to do Passwords Better
There is no single best way to do passwords. The best way for any particular person is a compromise between security, cost, and ease of use.
There are several parts to doing passwords better:
Have Unique Passwords
If one web site is hacked, that should not compromise your data at another web site. Web sites generally identify you by your username (or email address) and password. You could have a different username for every single web site you use, but that would probably be more confusing (and could possible lead to personality disorder). Besides, having to explain to your friends why you go by TrogdorTheMagnificent on one site butÂ TrogdorTheBold on another side would get tiring pretty quick.
For reasons which I hope are obvious, making your passwords unique is better than making your usernamesÂ unique. Unless you don’t want people to find you, then make both your username and password unique.
General Rule of Thumb
Passwords should be unique for each web site or service.
Why: If a unique passwords is compromised (e.g. someone hacked the site), the compromised password cannot be used to gain access to additional resources (i.e. other web sites)
If you’re asking yourself, “But how do I remember all those passwords?!” just hold your horses.
Choose better passwords
People suck…at picking good passwords.
, here’s a little test:
- in your password, give yourself 2 points .
- If you password has upper case, lower case, and numbers (or special characters), give yourself an additional 6 points.
- If your password does not contain any words from the dictionary, give yourself an additional 6 points.
- If you score 44 points or more, you have a good password!
- If you score between 21 and 44 points, your password sucks.
- If you score 20 points or less, your password really sucks.
The “goodness” of a password is measured by randomness, which is usually referred to as bits of entropy (which I cleverly disguised as “points” in the above test) the reality of the situation is that humans suck at picking their own passwords.
If more entropy leads to better passwords, let’s look at what leads to more bits of entropy in a password. The number of bits of entropy, H, in a randomly generated password () of length, L, is:
Where N is the number of characters possible. If you use only lowercase letters, N is 26. If you use lower and uppercase, N is 52. Adding numbers increases NÂ to 62.
mougiaswis an eight-character all lowercase password that has bits of entropy.
gLAviAcois an eight-character lowercase and uppercase password that has bits of entropy
Pr96Reguis an eight-character lowercase, uppercase, and numeric password that has bits of entropy.
Adding uppercase gets us 8 additional bits, but adding numbers only nets us 2 additional bits of entropy. However, look what happens when we just add additional characters instead:
vubachukusis a ten-character all lowercase password that has bits of entropy.
neprajubrawais a twelve-character all lowercase password that has bits of entropy.
For every additional character, you add bits of entropy. And unlike expanding the character set (e.g. using uppercase letters and/or numbers and/or special characters), you get more bits of entropy for every additional character you extend your password by…not just the first one.
The good news is that for randomly generated passwords, increasing the length by one character increases the difficulty to guess it by a factor of 32. The bad news is that for user selected passwords, every additional character added to make a password longer only quadruples the difficulty (adds roughly 2 bits of entropy which, based on NIST Special Publication 800-63 Rev 1 for the first 12 characters of a password).
Having to break out a calculator to determine the entropy of your passwords is not easy, and passwords should be easy. So let’s make it easy:
General Rule of Thumb<
Longer passwords (at least ten characters long) are better than more complex passwords.
Why: Adding complexity only provides a minimal and one time benefit. Adding length provides benefit for each character added and is likely to be easier to remember.
Track Your Passwords
The inevitable reality of doing passwords better is that you need a way to keep track of them. There simply is no way a person can keep track of all the different passwords for all the different sites.
This leaves us with two other options:
Write Down Your Passwords
Yes. Writing your passwords down in a safe place is an acceptable method of keeping track of your passwords:
Simply, people can no longer remember passwords good enough to reliably defend against dictionary attacks, and are much more secure if they choose a password too complicated to remember and then write it down. We’re all good at securing small pieces of paper. I recommend that people write their passwords down on a small piece of paper, and keep it with their other valuable small pieces of paper: in their wallet.
–Bruce Schneier, 2005
Writing down passwords can be appropriate because the most common attack vector is online (i.e. someone you’ve never even heard of trying to hack into your account from half-a-world away) with the following caveat: you make them more unique and more entropic.
By writing down passwords, you can increase their entropy (i.e. making them harder to guess) since you don’t have to memorize them. And since you don’t have to memorize them, you are more likely to create a better password. Additionally, if you write your passwords down, you don’t have to remember which password goes with which account so you can have a different password for each account: this also increases password uniqueness.
Encrypt Your Passwords
It would be reasonable to obfuscate your password list — instead of just writing them down in plaintext — so that if someone were to riffle through your wallet, they wouldn’t immediately recognize it as a password list or know exactly which passwords go with which accounts.
Instead of keeping them on a piece of paper, you could use a program to encrypt your passwords for you. There are a variety of ways to safely encrypt and store your passwords on your computer. I have been using 1Password for several years now and have been very impressed with their products7.
- Having lots of sensitive data stored in a known location on the internet is ripe for an attack.
- The defense against such an attack is predicated on the notion that the company has implemented their encryption solution correctly!
General Rule of Thumb
You don’t have to remember your passwords.
Why: It’s better to have unique and more entropic passwords than it is to never write down your password.
That’s it! Hopefully you found this helpful, now go make your passwords better and report back!0
Arguably, there is no one right way to do passwords ↩
it’s one thing to prove the mathematics of something, it’s a whole other thing to release a suitable product ↩
and still sort of is ↩
or your son/grandson/nephew/cousin ↩
this is, in part, how predictive typing technologies such as SWYPE work ↩
as well as their technechal discusions on topics such as threats to confidentiality versus threats to availability ↩