Before reading further... Are you looking for great Linux hosting from a company that cares about GNU/Linux? Pick Dreamhost hosting, get a 10% bonus to the disk space (and support Free Software Magazine in the meantime!)
Hard passwords made easy
Creating strong memorable passwords using mnemonic devices and word lists
Download the whole article as PDF
- 2005-03-25
- Server side | Easy
-
Write a full post in response to this!
In the online world, security plays a role in all online activities. Passwords are the most commonly used method to limit access to specific people. In my previous article I discussed assessing the relative value of systems protected by passwords, and grouping passwords across locations with similar trustworthiness.
In a nutshell, don’t bother creating and remembering strong passwords for low value systems, and certainly don’t use the same passwords for low value systems that you use in high value systems.
In this article, I’ll discuss how to create a strong password, and how to keep track of all your strong passwords, if you have a definite need to keep more than a couple.
In a nutshell, don’t bother creating and remembering strong passwords for low value systems, and certainly don’t use the same passwords for low value systems that you use in high value systems
Creating memorable strong passwords
A strong password is made up of several different types of characters, and isn’t a name or word in a dictionary. Many systems that require strong passwords will check any password you try to create against a set of rules. These rules often specify a minimum length, and that your password includes characters from at least three of the following four groups:
| Capital Letters | ABCDEFGHIJKLMNOPQRSTUVWXYZ |
| Lowercase Letters | abcdefghijklmnopqrstuvwxyz |
| Numbers | 1234567890 |
| Symbols | `~!@#$%^&*()_+=-[]|}{‘;:”/.,<>? |
Character Groups
The exact list of allowed symbols vary depending on the system. Some systems allow spaces in passwords, while others don’t. A particular system might also have an international character set that includes other letters or characters.
Time after time, people forced to use strong passwords come up with some gobbledygook thing like “v7GT%Xz2.” Leave a computer to generate a password for you, and you could well end up with something like that. And the next thing that happens is they’ve forgotten it and need to call the administrator for a new one. It’s certainly a strong password, but if you can’t remember it, and don’t store it in a safe place, it’s not an effective password.
I suggest using one of three strategies for creating strong passwords you can remember:
- Create a password using a mnemonic device
- Create a password using a word list with some variation
- Create completely random passwords and store them securely.
Use a mnemonic device
Remember learning about mnemonics? Not Ebonics, that’s something different. A mnemonic is a phrase or word to help you remember complicated or otherwise difficult to remember data. For example, ROY G BIV tells me the colors of the rainbow: Red, Orange, Yellow, Green, Blue, Indigo, and Violet—the letters in the name give you the sequence of the colors.
You can make up a phrase to remember a password, or make up a password based on a phrase that means something to you and nobody else
Jesus Christ Made Seattle Under Protest. No, not because there’s so many heathen folk running about—this is a local mnemonic for remembering the order of downtown Seattle’s streets, from south to north: Jefferson, James, Cherry, Columbia, Marion, Madison, Spring, Seneca, University, Union, Pike, Pine.
You can make up a phrase to remember a password, or make up a password based on a phrase that means something to you and nobody else. For example, our earlier “vhGT%Xz2” could become “Ve haven’t Gotten Ten percent Hex sleep, too!” or some similarly silly meaningless phrase. Our brains are capable of easily substituting one symbol for another. I wouldn’t trust this phrase for a password I only used occasionally, but for one you use several times a day, you’ll remember it in no time.
Write a full post in response to this!
Similar articles
Do you like this post?
Vote for it!
Copyright information
Verbatim copying and distribution of this entire article is permitted in any medium without royalty provided this notice is preserved.
Biography
John Locke: John Locke is the author of the book Open Source Solutions for Small Business Problems. He provides technology strategy and free software implementations for small and growing businesses in the Pacific Northwest through his business, Freelock Computing.
- Login or register to post comments
- 10066 reads
- Printer friendly version (unavailable!)




Looking for Linux hosting, reviews, coupons, etc.? See out user-voted list
Best voted contents
-
How do Drigg and Pligg compare?
Tony Mobily, 2008-08-17 -
The top 4 internet flame wars about free software
Andrew Min, 2008-08-16 -
What if copyright didn't apply to binary executables?
Terry Hancock, 2008-08-29 -
The Bizarre Cathedral - 18
Ryan Cartwright, 2008-08-17
Similar entries
Buzz authors
All news
Other sites
- The Top 10 Everything (Dave). The good, the bad and the ugly.
- Free Software news (Dave & Bridget). All about free software -- free as in freedom!
- Book Reviews: Illiterarty (Bridget). Book reviews, blogs, and short stories.
Hot topics - last 60 days
-
Don't compare GNU/Linux with Windows or MacOS - they are not in the same game
Ryan Cartwright, 2008-07-07 -
Self-signed certificates and Firefox 3 - a possible solution
Ryan Cartwright, 2008-08-05 -
Dictators in free and open source software
Tony Mobily, 2008-07-22 -
Why sharing matters more than marketshare to GNU/Linux
Terry Hancock, 2008-08-01 -
Why did Javascript/AJAX mop the floor with Java, Flash and Silverlight? Or, why open standards eventually win
Tony Mobily, 2008-07-30
Dedicated server
You're Storing Your Clients' Passwords on a PDA?
Submitted by Allen Moore on Tue, 2006-04-25 00:27.
Vote!If I understand this article, you're storing your clients' passwords on a PDA using a password vault with weak encryption. And in the event of a lost or stolen PDA, your recovery procedure is to "get a new one [PDA], restore your database, and change your passwords." Does this mean you have to go around to each client and change their password(s) as well? Perhaps I've misunderstood, but this doesn't seem like a very practical or safe solution.
3DES is weak?
Submitted by John Locke on Tue, 2006-04-25 15:10.
Vote!To respond to Allen (below):
That's a completely valid concern. The main point of keeping passwords on a PDA is because you can access them, and keep them relatively securely. The software I use and recommended encrypts the password database with 3DES, which, while not the latest and most secure protocol, is still strong enough encryption that it'll take an attacker a lot of computing resources, and many many hours to crack. It's still used by most SSL servers you visit on the Internet.
Losing a PDA is like losing a wallet--not something that happens often (hopefully), and involves some pain. Lose your wallet, and you need to go cancel all your credit cards immediately. Lose your PDA, and you have to go reset all the passwords. But by having it on a PDA, presumably you have a copy on your computer, as well, so you can quickly go down the list and do your damage control. And with an encrypted password store and a strong master password, you have at least several days or weeks to do this, if not years...
Besides, using SSH, I can "go around to each client and change their password(s)" from the comfort of my home office--one of the great things about Linux and FOSS software in general is how easy it is to remotely administer...
Do you have a better solution?
--
John Locke
Freelock Computing, http://www.freelock.com
The Open Source for Business Solutions