Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
7 Tips To Toughen Passwords
Threaded  |  Newest First  |  Oldest First
Osmore
50%
50%
Osmore,
User Rank: Apprentice
6/9/2012 | 5:39:23 PM
re: 7 Tips To Toughen Passwords
Some of you well-meaning authors need to recognize the real impracticality of your preachings. Some of us have well over 100 sites that we visit which require passwords, including this one. To do as you suggest is simply not practical. Why can't you come up with more meaningful ideas and get out of your ivory towers?
Mathew
50%
50%
Mathew,
User Rank: Apprentice
6/13/2012 | 9:45:46 AM
re: 7 Tips To Toughen Passwords
Hi Osmore, thanks for your comment. If there could be any single piece of advice that this author would propose, it would be: Use a password manager. No, it won't protect you if a site gets its password database stolen and cracked. But it does give you a practical, affordable way to generate and manage unique, strong passwords for the over 100 websites you use. That way, if your LinkedIn password does get published, it's a one-off. Inconvenient, but no one will be able to use it to access your Gmail account.
NanosecPeterS
50%
50%
NanosecPeterS,
User Rank: Apprentice
6/9/2012 | 6:59:54 PM
re: 7 Tips To Toughen Passwords
Maybe I am stupid, but I don't understand the logic what the author is talking about.
If the website ( they all should ) have a lock on the account after three unsuccessful password entry, so it doesn't matter how fast they can crack passwords. If the web-site doesn't have such a protection I simply don't want to enter any sensitive information there, that is all .
If the recovered password from the compromised web-site was not encrypted with the best possible encryption - that is not the user fault and the strength of the user password doesn't have anything to do with it.
ComScience
50%
50%
ComScience,
User Rank: Apprentice
6/9/2012 | 8:50:52 PM
re: 7 Tips To Toughen Passwords
"The best possible encryption" means a level of complexity, licensing and processing that is too expensive for most websites. You are probably thinking about military grade encryption?

Using MD5 is a standard encryption process, salted hashes should have been implemented and would have made the decryption much more difficult. See the wikipedia article for more information.

What the hackers did is convert the hashed password back into the text password using various processes including rainbow tables.

A simple explanation is if I make a password of "2Paramount109"and convert it to an MD5 hash, I get a 16 byte string of Hexadecimal characters that are the same no matter what MD5 conversion I use.

If I now have a list of MD5 hashes, I can see which ones match a table of pre-converted passwords. These huge tables of pre-converted passwords are called rainbow tables and can be generated using software at home, or purchased online.

They didn't actually try different login / password combinations on the live website, which could have locked them out of the website.

References:

http://en.wikipedia.org/wiki/M...

thecalitree
50%
50%
thecalitree,
User Rank: Apprentice
6/9/2012 | 8:52:22 PM
re: 7 Tips To Toughen Passwords
If you really want to know how to choose a correct password, look at this comic.

http://xkcd.com/936/

I literally just registered to post this.

The author of the comics is a physicist/computer scientist from what I can tell. Seems legit.

ANON1237925156805
50%
50%
ANON1237925156805,
User Rank: Apprentice
6/11/2012 | 9:02:57 PM
re: 7 Tips To Toughen Passwords
That's interesting because I was thinking of posting this very thing. It doesn't much matter how convoluted the algorithm you use to generate passwords: If they are 8 characters or fewer there's enough brute strength to hack them. It may take two days for yours as opposed to 1/2 hr for someone else's but the result is the same.

We need to move to passphrases. Passphrases needn't be unbearably cryptic as long as they are not trivial (e.g. "all cows eat grass" or "the password is swordfish"). One can string together words that are meaningful to them but not obvious to others.

Voila. It's memorized. To personalize for each site that has critical data, embed an abbreviation (not the full name) related to the site. For example, Facebook might have an fb in it or an ook. That's not risky in the context of a longer passphrase.

By all means punctuate your passphrase in an unpredictable way and/or throw in a cap if you like but only if you'll easily remember them.

The math for this is well documented. Longer string, MUCH harder to crack and more opportunity to create something that's easy to remember without being written down. End of story.

Why then do so many sites restrict password size to 8 characters? Why did Amex of all places reduced its max allowable password length from 8 to 6 a few years ago???!!!! Why do so many sites disallow spaces when by lengthening a passphrase they make it harder to crack it?

We need a new paradigm here, not more cryptic short passwords.
Bprince
50%
50%
Bprince,
User Rank: Ninja
6/9/2012 | 9:33:40 PM
re: 7 Tips To Toughen Passwords
Personally, I think the best thing to do is prioritize. Like Osmore is saying, there are a lot of sites that require passwords (such as this one). But this account probably isn't as important to you in terms of personal information etc. as your Facebook or email. So maybe come up with complex but memorable passwords for the important stuff and weaker passwords for the sites that are less important.
Brian Prince, InformationWeek/Dark Reading Comment Moderator
Eric_Brown
50%
50%
Eric_Brown,
User Rank: Apprentice
6/11/2012 | 12:55:13 PM
re: 7 Tips To Toughen Passwords
I have to argue with you, the biggest single security problem is articles like this one. I have to laugh by the fact that million articles about password strength and password managers the minute there are reports of passwords being stolen. HELLOGǪ anyone out there, the strength of your password or having it locked-up in Fort Knox does not mean anything when it is stolen from the source! You need to be talking about other steps like the need to implement some form of 2FA (two-factor authentication) were you can telesign into your account to protect you if your password were to be stolen. If they were to try to use the GǣstolenGǥ password and were not on the computer, smartphone or tablet you have designated trusted, they would still need the one-time PIN code which is delivered to YOUR phone via SMS or Voice.
Mathew
50%
50%
Mathew,
User Rank: Apprentice
6/13/2012 | 10:00:01 AM
re: 7 Tips To Toughen Passwords
Rock Star, you're entirely correct that websites need to do a better job of protecting their passwords, and two-factor is a great idea. So is using password encryption algorithms, versus cryptographic algorithms such as MD5 that are now widely used. Unfortunately, there's no magic wand ... with luck, the LinkedIn (et al) breaches will lead more companies to proactively invest, to help avoid any damage to their reputation when/if their password database gets knocked over. But from a consumer/user standpoint, using stronger passwords will at least slow attackers down, and making sure they're unique will prevent hopscotch-style password cracking attempts.
moarsauce123
50%
50%
moarsauce123,
User Rank: Ninja
6/11/2012 | 11:22:58 PM
re: 7 Tips To Toughen Passwords
Should do away with passwords altogether and use biometric access instead.
jleon570
50%
50%
jleon570,
User Rank: Apprentice
6/18/2012 | 10:01:50 PM
re: 7 Tips To Toughen Passwords
It seems to me that the biggest problem is the lack of security at the account host (aka LinkedIn, Google, eHarmony, Wells Fargo, Amex, etc). Yes, it is a bad thing if stupid ol' me uses the same "12345" for all my accounts from my eTrade account to my luggage. BUT, when the hacker community gets MY password, they have only MY password. As much as any technophobe would poke fun at me for my individual lack of security, the top 5 executives at LinkedIn, eHarmony, Last.fm, et al, need to be a proportionally larger laughing stock (because they're proportionally more stupid). In the web code I've been writing for at least the last 10 years, salting passwords has been universal, and (sadly) none of my sites hold a candle to LinkedIn in terms of subscribers or tech resources.

The entire internet development community needs to create and be generally aware of password protection standards, and web sites need a way to show the users that the site operators know those standards and to which level of protection they aspire. That way, I could tell my readers to stay away from banking sites that don't comply with say, "at least Password Protection Standards level 4 or higher, and 5 or higher is even better." I tell my readers that if the web site can send your actual password by e-mail if you forgot it, then every employee and business partner of that company already has your password. That would be "Password Protection Standards Level 0". So that morons like those at LinkedIn might be better aware, Level 1 would be an unsalted one-way hash or use of a weak hashing function (like MD5). Level 2 requires salted hashes using an unbroken and at least 160-bit one-way hash function. Level 3 requires salted hashes with a minimum of 48-bit salt using an unbroken and at least 224-bit one-way hash. Level 4, 5, 6, who knows. Maybe there should be other hash function requirements like resistance to collision attacks or preimage attacks, etc. But this protection would define only how well the passwords are stored and is meaningful only in the event that the password list is stolen.

The should be other descriptions of how the site protects its users, like: password entry is only allowed over a secure connection, password change enforcement, password length and diversity enforcement.

My password in MY possession is MY responsibility. My password in YOUR possession is YOUR responsibility.
Anne-MarieL355
50%
50%
Anne-MarieL355,
User Rank: Apprentice
12/7/2013 | 3:48:20 PM
Best advice i've ever heard on passwords....
Found very simple advice here.  This article says length beats complexity every time and is easier for you to remember: http://devnull1.blogspot.ca/2013/12/your-password-is-no-good.html 
MikeT951
50%
50%
MikeT951,
User Rank: Apprentice
10/17/2016 | 3:36:20 AM
Re: Best advice i've ever heard on passwords....
You also might want to use a random password generator such as this one bestpasswordgenerator That's the best way to create a secure and strong password.


Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11107
PUBLISHED: 2020-04-02
An issue was discovered in XAMPP before 7.2.29, 7.3.x before 7.3.16 , and 7.4.x before 7.4.4 on Windows. An unprivileged user can change a .exe configuration in xampp-contol.ini for all users (including admins) to enable arbitrary command execution.
CVE-2020-11444
PUBLISHED: 2020-04-02
Sonatype Nexus Repository Manager 3.x up to and including 3.21.2 has Incorrect Access Control.
CVE-2020-7617
PUBLISHED: 2020-04-02
ini-parser through 0.0.2 is vulnerable to Prototype Pollution.The library could be tricked into adding or modifying properties of Object.prototype using a '__proto__' payload.
CVE-2020-8835
PUBLISHED: 2020-04-02
In the Linux kernel 5.5.0 and newer, the bpf verifier (kernel/bpf/verifier.c) did not properly restrict the register bounds for 32-bit operations, leading to out-of-bounds reads and writes in kernel memory. The vulnerability also affects the Linux 5.4 stable series, starting with v5.4.7, as the intr...
CVE-2020-8423
PUBLISHED: 2020-04-02
A buffer overflow in the httpd daemon on TP-Link TL-WR841N V10 (firmware version 3.16.9) devices allows an authenticated remote attacker to execute arbitrary code via a GET request to the page for the configuration of the Wi-Fi network.