When it comes to securing yourself in your little digital world, everything revolves around your passwords. Your passwords are the first and major line of defense in securing your personal data be it email, documents, or even your money. The problem is, most people have fairly unsecure passwords and as a result their “front lines” are weak and easily penetrable. So how do we create secure passwords? What makes a password “secure”? And how many passwords should you have? We will answer all of these very important questions in this article.
Why You Need Secure Passwords
I get asked a lot when I go off on my diatribe about strong passwords because people think, “What’s the big deal? Let them read my email.” Well if someone can get access to your email, they can get a hold of a lot of information. Think about it, what goes to your email? Your bank information, PayPal, eBay, personal letters, maybe even personal info like social security numbers and addresses. Also, chances are the password you use for your email is the same one you use on at least a couple of those websites I mentioned. Even if it is not, if someone has your email address password, they do a “Forgot Password” where it will email the password or a link to change to a new password to your email address which they already have access to. So having a secure password on your email (for starters) is extremely important. You really do not want to stop there, you want as many of your passwords to be as secure as possible. Best practices recommends that you have a different password for every thing you log into. That can make things difficult to keep track of.
What is a Secure Password
Before we can really recommend that you use a secure password, we really should go over what exactly a “secure” password is. But even before we do that we must preface this with the following statement: a password is only secure as the person hiding it. If you tell others your password, it is no longer secure. Also, there is no such thing as a completely secure password. Any password can be cracked given enough time and resources. The real question is, do you want to make it easy for the person trying to get your password or make them work for it?
So with that in mind, a secure password contains the following:
- A combination of UPPER & lower case letters
- At least 1 number
- A special character like, !, %, ^, &, *, >, ~,`, or a #.
- Also, it is somewhere between 8-14 characters in length
Now, here is the downside, not all websites out there allow for passwords that contain special characters, so the best thing to do in those situations is to use a long password that contains letters and numbers, with the numbers placed through out the password rather than on the end or at the beginning.
Creating a Secure Password
So with those specifications in mind, how do we go about creating secure passwords that are easy for us to remember? The key is to use a password that really has nothing to do with you, this way a cracker can not figure it out easily. Fortunately for us, there are couple of websites that will help us create some secure passwords.
- PCTools Secure Password Generator: This website allows you to get real specific about your passwords, you can choose several options and interchange them at will. You can also pick a quantity so that you can get more than one password generated at a time.
- GoodPassword.com: Like the PCTools site, this website allows you to pick from some options for your password, but rather then get real specific you get to chose the length, and whether or not you want special characters. Also, if you have a favorite password or phrase, you can choose to create a “l33t” password out of that password or phrase. A “l33t” password is a word with some of the letters changed to numbers and special characters. This allows you to have a password you will easily remember, but is slightly more secure.
How Strong is Your Password
If you have some passwords you like, and they already contain numbers and letters in alternating case you can also check the strength of those passwords online using a couple of tools.
- Microsoft Password Checker: I will probably take some flack for this, but it doesn’t ask for a user name and it’s done with javascript so it is all client side. Just type in the password and it will tell you it’s strength.
- Javascript Password Strength Meter: This one is pretty nifty because it gives it a score and also a “points” breakdown about why your password is strong or weak. Again all client side so no worries about it going anywhere.
Knowing if you have a secure password can tell you if you need to utilize the password generators. If you have weak passwords, use the password generators to create a few stronger passwords.
Password Safes Preview
Like I stated earlier, best practices recommends that you have a different password for every thing you log into. That can make things difficult to keep track of. Something that can help you keep track of all these secure passwords would be a big help right? Well, there are programs out there called password safes that store passwords in an encrypted file so that you can only access the file with a password. We will be going into more detail about password safes next week, so be sure to come back for that.

Big Companies & Open Source
Last week, IBM announced that they would put somewhere around thirty developers on OpenOffice to help improve the product through bug fixes, new features, and collaborating with the OpenOffice team. The reason IBM says they are doing this is because they are seeing wide adoption of OpenOffice and it’s ODF (Open Document Format) by governments and companies the world over. But what makes this interesting is the fact that IBM is paying employees to work solely on an open source project, giving away features, code, and resources to a project that long term, makes them next to no money (if any at all). Big Blue seems to be doing this a lot lately. Why would a company do this?
I think that one of the many reasons that IBM has taken steps to help the open source community is because it is a good public relations move on their part. There are a lot of folks out there that support open source in a big way and as such, they support companies that support open source. People in the IT field that are pro-active in getting open source into their companies will recommend IBM products because IBM supports their favorite open source projects. Sure there are probably only a small percentage of folks out that are really trying to convince their C-people (CEO, CIO, & CFOs) into really integrating Linux and other open source projects into their IT infrastructure, but if you already have the larger percent why not try to woo the other smaller audience as well?
Another reason IBM might be doing things like helping OpenOffice and opening up their patent library to the open source community is because they believe in strength in numbers. The idea that someone might do what they did better, is not lost on them and they welcome someone to either do it better or innovate on top of it and come up with something completely new. In the end everyone eventually wins from this kind of behavior. Sure, it is okay to keep somethings proprietary (yes, I said that), but in the grand scheme of things, opening up stuff and helping out the open source projects, just helps make everything better.
Having IBM help out on the OpenOffice project also gives some much needed credibility to the OpenOffice suite and the ODF file standard. Just recently Microsoft lost it’s bid for ISO on their latest Office format, OOXML. And with the need for an open standard, ODF seems to be the next logical choice to push. It stands to reason that IBM might just be one of many large IT companies to task programmers with working on OpenOffice. A couple other companies are already spending time on it like, Red Hat and Novell. If IBM starts a trend to get other large IT companies to work on OpenOffice and other open source projects, you could begin to see a wider adoption of OpenOffice and other open source projects.
I think that this is a big step for the OpenOffice project, and I really anticipate what IBM is going to lend to the project and how much better OpenOffice will be as a result.