A Reasonable Password Policy for Ordinary People

Or: Humans Suck at Passwords

Humans Suck at Being Random

Humans, by our nature of having great pattern recognition, are terrible at detecting and generating true randomness. We have certain numbers that we prefer[1], we don't like clumps or sequences that can randomly occur, and we are also just generally bad at probability.

However, a common problem that haunts us requires a great deal of randomness to avoid catastrophe. This is of the selection of good passwords. When data breaches inevitably happen, a good password helps prolong the time between the breach being discovered and announced and hackers cracking the passwords, thus giving that necessary time needed to go in and change it.

But people are ass at selecting passwords.

Humans Usually Suck at Choosing Good Passwords

Passwords are usually not stored directly as text on company servers;[2] they are put into a mathematical function that converts any string of characters into a unique number; this is called a hash, and the function that produces it is called a hash function. When you try to log in, your attempted password is sent to the server, the server puts your password through the hash function, and if that number matches the hash on file, you are then let in.

This prevents any intruders from immediately gaining access to your passwords and trying them on every other account of yours on the great web. To recover the plain-text of a password, a hacker must randomly try every possible combination of password by putting it in the hash function and checking if it matches.[3]

However, since most humans are not random at all, there are very few combinations that a hacker-cracker must actually try in order to recover a password.

There are the trivial ones that people choose, like "password", "123456789", "admin", or any of the like that are pretty much amongst the first passwords that hackers try. Then there are names, birthdays, and nouns. Check out the Wikipedia page for the List of the most common passwords article.

For the rest, since there are (relatively) so few Latin-characters, numbers, and symbols and the fact that modern GPUs can generate hashes of possible passwords at a rate of hundreds of thousands to billions hashes per second, having a short password of 7 characters could lead to it being cracked in about 2 days.

However, that estimate is based on the assumption that the password was made up of all uppercase letters, lowercase letters, digits, and the symbols of !@#$%^&*() in a perfectly random way. However, because we're humans, we tend to use these characters in quite predictable manners. An uppercase letter at the beginning of the password, a number at the end of a password, and maybe an exclamation point at the end if one is feeling particularly spicy. Those more industrious folk might substitute a ! for a 1, a 3 for an E, a @ for an a, which only adds about 1 or 2 predictable combinations that a hacker needs to try.

And given that many people like to use words as their password, hackers can use so-called dictionary attacks to try every word in the dictionary. Although there may be a million words in English, most words that a person would reasonably choose would only come from maybe the top 10,000 words if we are feeling particularly generous. 10,000 combinations is less than a quarter second for modern attacks to crack.

The National Institute for Science and Technology recommends a minimum 15-character length password. Also, they no longer recommend having such rules rules like "Have least one number" because the way in which people are predictable in implenting those rules actually tends to reduce password strength (see above).

Humans Suck at Memorizing Random Characters

Even if one were to generate a random string of characters like "YFyoJD/iTpYwWUtu5nnC93clhioN8wMyFJZwuYfds62QF+1DMXr7I5I6CXSSSY3LNhe9Q4tgFZz5yPc20BjsCA", the problem is memorizing it. Humans are not particularly good at naturally remembering long strings of random characters strung together unless you employ such tactics such as chunking, mnemonics, or memory palaces.

But ain't nobody got time for all'at. People end up writing stuff down on sticky notes. That's fine if you're not in a public area, but if you are...

What Can Be Done?

The first option is to offload the computational effort of generating and memorizing stuff to a thing that is particularly optimized to generate random numbers and store long strings of information.

You can use a trusted password manager like Bitwarden or Apple's own password manager to both generate random passwords and securely share them across your devices.

But how about the password for the password manager?

Getting Strong Human-Memorizable Passwords

This is where we can exploit human pattern recognition.[4] Humans are good at memorizing words; if we combine a bunch of randomly selected words, we can get a 4 word password that adds up to over 1016 combinations given an initial word bank of 10,000 words. Each word multiplies the number of combinations by 10,000. And a nice property of English words is that they are rather long, so we can easily meet the 15-character recommendation and thus also protect against those who may just try every single combination of alphabetical characters.

I would say it's easier to memorize "fuzzilyyowlsblimpcorrie" than "u2ptahRydy/IUcUQWSgpeOROoAYlc5j9VbNMZkso7BwwqnzTbu//OgOWzFfVJVzoeUg8Y84".

The cool thing with Bitwarden is that it has a built-in tool to randomly generate passwords along the way of this scheme.

The trick is getting random words from a trusted source. You could get them from a website like randomwordgenerator.com. However, if you are a bit paranoid, consider the possibility that people behind the website may have tweaked the selection to not truly pick random words, thus making your password susceptible to being cracked.

You could find a word list online, get a trusted random number generator from some place like random.org, and use it to randomly select words from the list by generating a number from 1 to the number of words in the list and selecting the words based on the word that corresponds to your 3, 4, or 5 randomly generated numbers.

Those with a macOS, Linux, or other kind of Unix box could run the following shell pipeline to be run in a terminal to select 4 random numbers from the system's word list (given you have the GNU Coreutils installed in order to have shuf):

shuf /usr/share/dict/words | head -n 4

Footnotes

  1. ^ Cf. the number 7 and 37 being amongst the most commonly chosen 'random' numbers.
  2. ^ And if they are, we have much bigger issues.
  3. ^ This is an oversimplification.
  4. ^ Á la xkcd 936.

Tags