Largest-Ever Password Study: We Are All Idiots

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
Some things are inevitable like death and taxes…..and weak passwords. According to a new study that took a look at 70 million Yahoo users accounts, nothing much has changed in the password encryption arena: we still suck. :D

“We find surprisingly little variation in guessing difficulty; every identifiable group of users generated a comparably weak password distribution.”
 
This is why two factor, or pass card or biometrics are becoming increasingly popular.. however physical items cost lots of money and limit cases where they can be used... Same for biometrics, and on top of that biometrics have accuracy issues.
 
LongPassword.jpg
 
I used to use 2 passwords; 1 for important sites (email, bank, Paypal), 1 for everything else.
Now I've started using those same 2 passwords, tweaked depending on what it's for.

I also started using LastPass with the hope of picking a bunch of random shit for every site and using different passwords for everything. The problem with that is, I didn't realize until just now that there's a LastPass for Android, so until now I'd have to remember passwords to login with my phone which is why I haven't done that yet.

Generally I think the fuss over password complexity is little more than FUD. Sure, don't just pick 1234, password, or asdf for your password. However, I think the whole idea of 12+ characters plus random stuff is just a little overkill. The other problem is, between all the sites I use, some of them actually have complexity requirements (or don't allow special characters) which screws up my ability to remember passwords for everything else, because I can't use the semi-'one size fits all' idea that I've kept with for so long.
 
I used to use 2 passwords; 1 for important sites (email, bank, Paypal), 1 for everything else.
Now I've started using those same 2 passwords, tweaked depending on what it's for.

I also started using LastPass with the hope of picking a bunch of random shit for every site and using different passwords for everything. The problem with that is, I didn't realize until just now that there's a LastPass for Android, so until now I'd have to remember passwords to login with my phone which is why I haven't done that yet.

Generally I think the fuss over password complexity is little more than FUD. Sure, don't just pick 1234, password, or asdf for your password. However, I think the whole idea of 12+ characters plus random stuff is just a little overkill. The other problem is, between all the sites I use, some of them actually have complexity requirements (or don't allow special characters) which screws up my ability to remember passwords for everything else, because I can't use the semi-'one size fits all' idea that I've kept with for so long.

Password complexity is a relic from the 90's when password cracking was popular. Doesn't really matter much these days as long as you're not using an OBVIOUSLY easy password such as 1234, and even then that's unlikely to matter unless you're being targeted specifically. Someone getting into your account is much more likely to happen now via keyloggers, not through brute forcing a weak password.
 
According to a new study that took a look at 70 million Yahoo users accounts...
Don't need any other information than that.
 
Speak for yourselves. I have no trouble with my passwords and they are quite strong.
 
I use lastpass, with a 17 character master password. Benefits are all my sites have random, long passwords I could never remember, and because lastpass saves user/pass per URL, you don't have to worry about being phished. If an email sends you to a phishing site, lastpass won't know the URL so won't enter a password which is too complicated to remember so I won't enter it either.
For anyone curious, lastpass stores passwords on a server, but the client encrypts them by your master password before they get uploaded, so it's pretty safe even if their servers are hacked.
 
I use lastpass, with a 17 character master password. Benefits are all my sites have random, long passwords I could never remember, and because lastpass saves user/pass per URL, you don't have to worry about being phished. If an email sends you to a phishing site, lastpass won't know the URL so won't enter a password which is too complicated to remember so I won't enter it either.
For anyone curious, lastpass stores passwords on a server, but the client encrypts them by your master password before they get uploaded, so it's pretty safe even if their servers are hacked.

a local infection would still compromise lastpass, and since local infections are how many passwords fail I don't quite see the point.
 
a local infection would still compromise lastpass, and since local infections are how many passwords fail I don't quite see the point.

A local infection would compromise any password scheme I know of. My main appreciation of lastpass is you can't get phished, if a site does something stupid like using plain-text to store passwords (it's happened before, and there's no way for the user to know before hand) you don't have to worry about other sites you used that password on being compromised, and the difficulty in remember passwords even if you use the same one as some sites require a number, some a special character, others forbid numbers and special characters, some only allow 8 chars which would be too short to use everywhere and so on.
 
So the combination is... one, two, three, four, five? That's the stupidest combination I've ever heard in my life! That's the kind of thing an idiot would have on his luggage!
 
So the combination is... one, two, three, four, five? That's the stupidest combination I've ever heard in my life! That's the kind of thing an idiot would have on his luggage!

1, 2, 3, 4, 5? That's amazing! I have the same combination on my luggage!

<_<

>_>
 
You can't use use brute force to find passwords on websites, so there's no more than a few "too simple" passwords. And, insanely complex passwords are often undermined with invitations to give easy-to-guess/social-engineer/research security questions to retrieve a lost password.
 
Don't need any other information than that.

Yeah, a guy commenting on the article got it right:

Dave Park said:
"analyzed the password strength of about 70 million Yahoo users" Uh, doesn't that skew the sample results downwards? That's like polling an advanced mathematics aptitude test at a truck stop.
 
LOL

Spaceballs....you know you love to quote it.

Still waiting for Spaceballs 2...The Search for More Money. ;)


I hear that. The wait is like waiting for DNF...just hope the sequel isn't the same as DNF. :eek:
 
I just wish that some of these articles would place SOME blame back to the websites. As was mentioned earlier, many have different requirements. And the ones that restrict the max length or refuse symbols are just asinine.

I bought Roboform before free version got popular, and I have that synchronized between all of my computers. I couldn't guess my email password to save my life. It is 63 characters of gobbledygook. Many accounts, like my bank, even have the username in gibberish. Max 8? Okay then, 8 characters of gobbledygook. No symbols? Okay, drop that option from the random generator. Makes me want a url shortening service for passwords, it would be one very smart cookie to make that work. :)

Roboform syncs in the background whenever a change is made, so I can then go to another computer launch the browser(so it triggers Roboform and it syncs), and then it can log me in to that site.

If the computer is compromised, all bets are off, for everything. That's like playing Russian Roulette. You cannot be protected from your own mistakes, or stupidity.

We never had to remember our car keys, or house keys, we just had to remember to take them with us. Everybody should have a digital keyring.
 
complexity is silly when people use the same 'complex' password across numerous entities and a random hack against some neglected web facing database will pump it out into a txt file. i know many people who use their exact email/pass combination on every website they visit.

it's a pain in the ass at times but i use a completely different password string for any 'important' site (bank, CC, etc) i need to log into.
 
A friend hosted a website for me years ago. It got hacked, and afterward I found out that the database password was only a 4 character alphanumeric. I was more than a bit unhappy about that. It was promptly changed to something even the NSA would have trouble guessing. Stuff is going to get hacked, sure, no software is perfect, but that was like leaving the freaking keys in your front door.
 
Bonneau suggests that people chose a randomly selected number at least nine digits long because it will be easy enough to remember like a phone number and still provide a an above-average level of security

This made me cry. Do they have any idea how easy it is to brute force 9 characters? And that's not something that takes much skill, an average script monkey can do it.

Still, the article has a point. Way too many people still use "password" or "whatever20##" as if they were real passwords.
 
This made me cry. Do they have any idea how easy it is to brute force 9 characters? And that's not something that takes much skill, an average script monkey can do it.

Still, the article has a point. Way too many people still use "password" or "whatever20##" as if they were real passwords.

But as long as you don't use something obviously stupid like "password" on a major website with a bare minimum of security, you're secure.

Any real brute-force attempts would be detected, and you'd get a password reset request link in your email. As long as the site stops you from entering the exact same password again, security is maintained.

This emphasis on 8+ character/symbol/numeric mixed passwords is pure bullshit. All this posturing is based on the assumption that hackers will steal the data store and have all the time in the world to brute-force your account...but that really doesn't happen often on reputable websites.

And when shit like this DOES happen, it's usually pointless to have a strong password because the company dopes something incredibly stupid like not encrypting sensitive data.
 
How secure are random pass phrases vs just a password, like "Idrivearedcarsinceitisfast"
 
But as long as you don't use something obviously stupid like "password" on a major website with a bare minimum of security, you're secure.

Any real brute-force attempts would be detected, and you'd get a password reset request link in your email. As long as the site stops you from entering the exact same password again, security is maintained.

This emphasis on 8+ character/symbol/numeric mixed passwords is pure bullshit. All this posturing is based on the assumption that hackers will steal the data store and have all the time in the world to brute-force your account...but that really doesn't happen often on reputable websites.

And when shit like this DOES happen, it's usually pointless to have a strong password because the company dopes something incredibly stupid like not encrypting sensitive data.

I would agree that much of the lapse in security is server side, but I disagree that simple/non-mixed case passwords are ever secure for several reasons: word lists, rainbow tables, and even just guessing (for simple passwords such as "password"). Also you have to consider what happens if someone manages to grab the hashes, which happens to even more secure companies/servers quite often. In that case, the length/makeup of your password is going to make a considerable difference as all options would then be available including brute force.
 
How secure are random pass phrases vs just a password, like "Idrivearedcarsinceitisfast"

I would say exponentially. You can do some googling for details, but there are three primary direct attacks against a password. It is true that a secured server should detect these and time them out or block them, but many do not.

Brute force, wordlists, and rainbow tables (similar to wordlists) all work best once the hash is obtained of course. Basically each new character set you add to your password makes each of these methods take significantly more time, and eventually makes them unrealistic.

Again, a lot of this should be done server-side (such as password salting), but often it is simply not done.
 
I have a fairly short but random password for my gmail account.. it got hacked and spams were sent from it. I then reset my password to a password of 20 character length with letters and numbers.

That lasted about a year before it was hacked again.

Now it is even longer... waiting to see how long that lasts until it is hacked again.

And no, I wasn't keylogged nor do I use the same password anywhere else.
 
I have a fairly short but random password for my gmail account.. it got hacked and spams were sent from it. I then reset my password to a password of 20 character length with letters and numbers.

That lasted about a year before it was hacked again.

Now it is even longer... waiting to see how long that lasts until it is hacked again.

And no, I wasn't keylogged nor do I use the same password anywhere else.

"have" in first line was supposed to be "had".. stupid no edit buton for front page posts.
 
Some things are inevitable like death and taxes…..and weak passwords. According to a new study that took a look at 70 million Yahoo users accounts, nothing much has changed in the password encryption arena: we still suck. :D

You don't get to say "we" in an all inclusive manner when they looked at yahoo accounts. :D
 
I have a fairly short but random password for my gmail account.. it got hacked and spams were sent from it. I then reset my password to a password of 20 character length with letters and numbers.

That lasted about a year before it was hacked again.

Now it is even longer... waiting to see how long that lasts until it is hacked again.

And no, I wasn't keylogged nor do I use the same password anywhere else.

Any chance you got hit by a cookie stealer, cross site scripting, etc . . .? Or just basic phishing. If you leave your google account always logged in and don't use https everywhere along with noscript or something those are possibilities. It's highly unlikely someone actually cracked your password if it was 20 characters long.
 
How the hell did this 3rd party get all these unencrypted passwords from Yahoo? :eek: :mad:

The quote was shamelessly stolen from IMDB. It's one of the best movies ever made. :)
You mean the quote was "ludicrously" stolen from IMDB, right? ;) Yeah, that movie rocks. Just a great movie. :cool: Too bad the DVD transfer isn't that good. :(
 
Another big issue that is often overlooked is brute force protection. The system in question should block the IP and/or raise flags if any user gets the password wrong more than a certain amount of time.

Even the most secure password will eventually be guessed if the system does not stop brute force attacks. It could take years but they'll eventually get in. Open SSH up to public, even a secure protocol like that and the system will eventually get hacked if there is nothing in place to stop brute force protection.

How the hell did this 3rd party get all these unencrypted passwords from Yahoo? :eek: :mad:
I was thinking the same. I think THAT alone is a bigger problem then anything else. Does Yahoo just give this away if someone asks? Also a proper system should not store passwords in plain text, either. They should be stored in an unreversable hash. The nice thing with passwords is the system does not actually need to know what it is, it just needs to be able to take user inputted data and transform it using the same algorithm, so if it matches then the user entered the right password.
 
...

I was thinking the same. I think THAT alone is a bigger problem then anything else. Does Yahoo just give this away if someone asks? Also a proper system should not store passwords in plain text, either. They should be stored in an unreversable hash. The nice thing with passwords is the system does not actually need to know what it is, it just needs to be able to take user inputted data and transform it using the same algorithm, so if it matches then the user entered the right password.
Yes, that's the angle I was also coming from. Even if there are no IDs associated with the passwords, it's not good if Yahoo purposely or accidentally gave that list of unencrypted passwords. No one should know what the passwords are, not even the system. It should be a hash like you said and when someone enters his password, its hash should match what's on the system. No person or computer other than the user should know his password.
 
I have a fairly short but random password for my gmail account.. it got hacked and spams were sent from it. I then reset my password to a password of 20 character length with letters and numbers.

That lasted about a year before it was hacked again.

Now it is even longer... waiting to see how long that lasts until it is hacked again.

And no, I wasn't keylogged nor do I use the same password anywhere else.
You know that just because you're listed as the sender, doesn't mean they came from your account. Are you sure its coming from your account other than people receiving the spam with your address. Like copies in your sent folder or something?

Your address as sender can be spoofed from just about anywhere. Some recipients might be able to authenticate it, I believe, but many do not.

In fact, smart e-mail hack would grab someone's address book and then use one of the addresses to be the sender. So the really compromised account goes undetected longer. So it may not even been your doing in away shape or form. Some one who had your address in their e-mail somewhere it all it took.
 
That does come back to my saying about brute force protection. As far as I know most online services like gmail do not have any kind of protection against it. Bots will use known usernames and just start randomly guessing passwords, until they eventually get in. It can take 10+ years, but they will eventually get in.
 
How secure are random pass phrases vs just a password, like "Idrivearedcarsinceitisfast"

Depends on the length of the random password. I personally like passphrases like the one you wrote, because they are easier to remember and provide a lot of security.
That pass phrase would take 3.33333333 × 1022 seconds at 30M guesses per second (typical computer guessing speed) assuming the attacker knew it was 9 words and had a dictionary of the 1,000 most common english words that included those words.
You would need a random password (or at least a word that is not in any hacker dictionary) of 19 alphanumberic characters to match it's security, and that is a lot harder to remember usually than the passphrase, again assuming the hacker knows you have 9 words in the passphrase and has all of them in a 1,000 word list. To make it even better, add a random number in a random place, e.g.: "Idrivearedcars4inceitisfast" - even one non-word in the pass phrase would kill the dictionary attack totally and send it's guessing difficulty off the scale.
 
3.33333333 × 1022 = 3.33333333 x 10^22, hardforum discarded the exponential formating.
 
Back
Top