Friday, December 17, 2010

Write your passwords down

Here's my advice on password security based on the collected opinions of others:

1. Write them down and keep them in your wallet because you are good at securing your wallet. (ref)

2. Use different passwords on every web site because if you don't one site hacked = all your accounts hacked. (ref)

3. Use passwords of at least 12 characters. (ref)

4. Use mixed-case, numbers and special characters. (ref)

Research says you need 80-bits of entropy in your password so it needs to be long, chosen from a wide range of characters and chosen randomly. My scheme gives me 104 bits of entropy.

My passwords are generated using a little program I wrote that chooses random characters (using a cryptographically secure random number generator) and then printing them out on a tabula recta. If you were to steal my wallet you would find a sheet of paper that looks like this in it (I have a second copy of that sheet left with a friend in an envelope):


I use that sheet as follows. If I'm logging into Amazon I'll find the intersection of column M and column A (the second and third letters of Amazon) and then read off diagonally 16 characters. That would be my Amazon password (in this case, TZ'k}T'p39m-Y>4d); when I hit the edge of the paper I just follow the edge).

The security of this system rests on the randomness of the generated characters and the piece of paper.

PS Yes, it's a total pain to use long, random, different passwords.

PPS If it's not obvious to people you can add a second factor to this (something only you know) in the form of the algorithm for picking the password from the sheet. For example, instead of using the second and third characters from the site name you could pick any combination. And you could change the letters as well (e.g. for Amazon you could use the last two letters moved on one place in the alphabet; you'd have PO as the key). Also you don't have to read diagonally but could use any scheme that works for you (e.g. a spiral pattern, read vertically, read characters at offsets from the start based on the Fibonacci sequence, etc.).

Labels:

If you enjoyed this blog post, you might enjoy my travel book for people interested in science and technology: The Geek Atlas. Signed copies of The Geek Atlas are available.

22 Comments:

Blogger RBerenguel said...

Good approach (I saw a very interesting site that generates cards like yours, by the way, but I don't have the URL at hand). I follow another scheme... I use phrases from some book I know almost to heart. Like a 30 or 40 characters long phrase, with random case changes (far lower entropy than your method, I guess). And I don't write them down, becase I already know them, or can look them up. But I like your approach... I think it is time to upgrade my method.

Cheers,

Ruben
Latest in my blog: The emacs 30 day challenge: using gnus to read email as a newbie

5:19 PM  
Blogger Ixmatus said...

I like the table approach. I've always written down passwords - I've believed for some time that having your passwords WITH you is better than having the same/easy passwords that you can remember.

I store a copy of my password list in my fire proof safe at home, and the really common ones (Amazon, my computer, banking, GPG key, etc...) I've memorized the pattern on my keyboard...

5:37 PM  
Blogger Paul Robinson said...

Isn't it better to use a password manager like 1Password (use any length of password) with the encrypted password file stored in Dropbox for cloud recovery?

6:01 PM  
Blogger PaulH said...

I am trying the open source password store Keepass. It seems to do what you recommend regarding password generation, but its printing capabilities are very limited - nothing even close tabula recta. I like the idea of a cryptic hard copy. Portable and no chance of a crash. :-)

6:19 PM  
Blogger J. Aaron Farr said...

I tend to use romanized Mandarin Chinese phrases which I then convert some into leet-speak. It tends to create long, complex passwords that are very easy for me to remember.

6:26 PM  
Blogger jockc said...

I like this idea, but it might be a little inconvenient. I recently saw a blog post somewhere with another good scheme for writing down passwords safely. You have a 3-4 character 'secret part' suffix and a 3-4 letter ID prefix part. The secret part is not written and is the same for all passwords. So let's say my secret part is 'xyz'. To write down my Amazon and Bank of America password I would write something like:

AM4zxidj3
B0f4ie7ix

^^^^
(ID part)

the actual passwords would be xidj3xyz and ie7ixxyz. Of course you could do variations like instead of having a fixed secret part, use the ID part reversed or something.

6:26 PM  
Blogger kibitzer said...

Can you explain how the piece of paper is more secure than, for example, KeePassX or a similar cross-platform password storage tool which lets you generate arbitrary length passwords (I use 20+ usually)?

It seems practically easier to steal the password from your wallet than to decrypt password database.

8:28 PM  
Blogger Wojtek said...

This is nice for the geeky "do it yourself and forget the wallet at home" section.

For the lazy rest of us there is, thanks God, Lastpass (http://lastpass.com)

9:51 PM  
Blogger Mathew said...

Innovative system for remembering them. For when I'm at a computer I use KeepassX where the database is stored on my dropbox account.

10:40 PM  
Blogger Sullof said...

I think that using password schemes is bad. Because in order to be useful, the method needs to be fast, simple and replicable.
Suppose that someone creates a fake website in order to grab one of your smart passwords. If he understands that you use a method, he will try to deconstruct the method based on the fact that his website surely is included in some manner in the password itself.
Also, since many people who use these methods tend to divulge them to the community, there isn't even a need to create a fake website to understand your passwords.
The only solution that really works is to use a password manager. My favorite obviously is Passpack, because I am a co-founder, but regardless of which software you choose the important thing is that you use it.
My advice is not to relay on any clever schemes because you may be in for a bad surprise.

4:09 AM  
Blogger pat said...

I use the same 6 and 8 character passwords on every site I visit (1000s) and have never had a problem. What a pain to follow those steps. No thanks.

6:44 PM  
Blogger Derek said...

Pat,
The problem with using the same password for different sites is that your password is only as strong as the weakest security in any one of those sites. See the recent Gawker problems for a perfect example.

1:03 PM  
Blogger max.countryman said...

I was inspired to write a little Python script that generates a tabula recta and finds a password based on a row and col intersection, as described in this post.

The challenge now is finding a better PRNG. Python's random module uses the Mersenne Twister (not suitable for cryptographic uses), however the SystemRandom class makes use of os.urandom, which in some cases (think OS X, FreeBSD, OpenBSD) makes use of the Yarrow algorithm, a well known CSPRNG.

5:23 PM  
Blogger X said...

How does this work in conjunction with sites that have different rules? Some sites only allow passwords of up to 11 characters, and if your approach requires 16 characters, how are you going to remember that a site requires at most 11?

7:03 AM  
OpenID bootload said...

Q John, would /dev/random [0] on linux or /dev/urandom accessed via python random.SystemRandom [1] in Python pass your CSPRNG requirement?

[0] http://en.wikipedia.org/wiki//dev/random#Linux

[1] http://svn.python.org/view/python/branches/release27-maint/Lib/random.py?view=markup via http://docs.python.org/library/random.html

6:02 AM  
Blogger Yogsototh said...

I saw your post about your mail Canary and it sent me here.

Your method for managing password seems both not so secure and difficult to use.

Not so secure, because, for example, your password for Amazon and Imazomby is the same.
Furthermore with a sufficient amount of data, I can retrieve you main super password (the sheet of paper).

Of course, your method is far more secure than what most people do. But you should take a look at my method.

http://yannesposito.com/Scratch/en/blog/Password-Management/

Every password is just at one copy/paste. But yes, you need to remember only one strong password (which you might have written somewhere).

You can have 40 character long very easily. I use this method for some years now, and I am really happy with it. While I am certain it is both easier and more secure than your method.

Best.

4:22 PM  
Blogger John Graham-Cumming said...

That's very similar to the technique I used in my program called quepasa http://quepasa.sourceforge.net/

I agree with the weakness in my password scheme that some passwords overlap. Note that in your scheme the security will rest on the master password you choose as SHA1 is very fast and it would not be hard to recover your original password given a ( site, password ) combination that got leaked.

4:32 PM  
OpenID Andrew said...

Thanks for the great post. In case others find this idea interesting, I built a tool called passtab to generate these Tabula Recta's in PDF for printing (with some additional features). Cheers!

3:42 AM  
Blogger Jacob MacElroy said...

I am sure other things exist but here is a quick python script for creating your own random tabula recta.

8:36 PM  
Blogger skyriser said...

Cool, reminds of our iPhone app "Password Grid": http://passwordgrid.com/

1:52 PM  
Blogger garg oyle said...

Hi, I stumbled across this post on Lifehacker.com. Do you make your program to generate a tabula recta public?

What does one need to generate a random number?

In essence how do I get this to work for me? How about a step by step for the unwashed masses?

9:45 PM  
Blogger Doug Fraser said...

Lastpass + Yubikey

I still use a long twenty character mix of letters, numbers and special characters that are symbolic to me, but senseless to anyone else.

Yubikey gives it a second factor.

7:22 PM  

Post a Comment

Links to this post:

Create a Link

<< Home