Live data from Hacker News

LinkedIn password leak

usblog.kaspersky.com

71–80 of 218 posts

Re: LinkedIn password leak

#71
post #42

Earlier quoted context omitted.

I received none.

That means either a) You're account was not included in the comprised accounts or b) You checked an email different from your LinkedIn account.

I didn't get an email until after I logged into my account with the compromised password. Then it sent me an email and locked my account. Sort of odd way of dealing with the problem.

This all happened about 20 minutes ago.

Re: LinkedIn password leak

#72
Aaaand that's why I use 'pwgen -s 22' to generate a unique password for every single site I use. I don't care if a salted password database is stolen; heck, as soon as I change my password I don't even care if a plaintext database is stolen.

Why -s? Because it means each password is a complete word, and may easily be double-clicked in a password list (which is nice, because selection is copy in X).

Why 22 characters? Because 22 mixed-case letters and digits are just over 128 bits of entropy.

Say it with me:

    pwgen -s 22

Re: LinkedIn password leak

#73
post #6

Woo, I created my LinkedIn profile in 2015, so I should be safe since the leak is supposedly from 2012. If anyone else isn't sure when they made their LinkedIn, you can see your join date here (ctrl+f "Member since"): https://www.linkedin.com/psettings/

Just had my 10th anniversary a few days ago.

Re: LinkedIn password leak

#74
post #50

1: Change your password. RIGHT NOW. If you’re not sure how strong your password is, test sample passwords with our password checker here. Seriously? Keep in mind that these estimates are based on some bogus entropy estimation. If a password hacking guy runs the correct dictionary past the hashes you password generates, it might be as small, well, as the first one tried. For example, run the passphrase Ph'nglui mglw'n…

Aren't cracks of this nature thwarted by salting?

No. Salting mostly prevents rainbow tables from being very useful, but rainbow tables are questionably useful anyway with modern hardware. (Obviously depending on the type of the hash)

Re: LinkedIn password leak

#75
post #50

1: Change your password. RIGHT NOW. If you’re not sure how strong your password is, test sample passwords with our password checker here. Seriously? Keep in mind that these estimates are based on some bogus entropy estimation. If a password hacking guy runs the correct dictionary past the hashes you password generates, it might be as small, well, as the first one tried. For example, run the passphrase Ph'nglui mglw'n…

So, being one of the people who hovers around laymanship when it comes to these questions, how hard is it to crack a randomly generated 25 character string with 5 digits and 5 symbols? This is typically what I would use for a website.

Such a password has about 157 bits of entropy, which is far too big to be found by any kind of brute-force approach.

Of course there are other ways that a password can be cracked, for example an attacker who breaks into the server can capture it as it is submitted. So it's still worth having a different password for each site.

Re: LinkedIn password leak

#76
this might be a dumb question - but if the password was unique to that account AND you have 2 factor auth enabled, is there any reason you need to change the password ?

so if some hacker somehow manages to backward engineer a salted-bcrypted-hash of my unique password, he still cant get in without my cell phone

Re: LinkedIn password leak

#77
post #72

Aaaand that's why I use 'pwgen -s 22' to generate a unique password for every single site I use. I don't care if a salted password database is stolen; heck, as soon as I change my password I don't even care if a plaintext database is stolen. Why -s? Because it means each password is a complete word, and may easily be double-clicked in a password list (which is nice, because selection is copy in X). Why 22 characters?…

Good for you. Too bad most people can't even be bothered to use more than a couple variations of the same password.

This is an area that will get much more attention in coming years as technology finds better ways to authenticate us instead of using secret codes we have to remember.

Re: LinkedIn password leak

#78
post #74

Earlier quoted context omitted.

Aren't cracks of this nature thwarted by salting?

No. Salting mostly prevents rainbow tables from being very useful, but rainbow tables are questionably useful anyway with modern hardware. (Obviously depending on the type of the hash)

Yeah but isn't this method just a giant rainbow table whose source is crawlable web content?

>It would have been impossible to use a brute-force attack or even a combined dictionary to crack a phrase of that length. But because the phrase was contained in this Wikipedia article, it wound up in a word list that allowed Chrysannthou to crack the phrase in a matter of minutes.

Re: LinkedIn password leak

#79
post #28
post #6

Woo, I created my LinkedIn profile in 2015, so I should be safe since the leak is supposedly from 2012. If anyone else isn't sure when they made their LinkedIn, you can see your join date here (ctrl+f "Member since"): https://www.linkedin.com/psettings/

2009... Awesome. Linkedin should probably be the one warning me about this, but I never heard of this before. Edit: filtered as Spam, nevertheless they should have locked my account.

Glad to hear your Spam Filter work fine!

Re: LinkedIn password leak

#80
post #72

Aaaand that's why I use 'pwgen -s 22' to generate a unique password for every single site I use. I don't care if a salted password database is stolen; heck, as soon as I change my password I don't even care if a plaintext database is stolen. Why -s? Because it means each password is a complete word, and may easily be double-clicked in a password list (which is nice, because selection is copy in X). Why 22 characters?…

I use KeePass' password generator, which defaults to generating random sequences of 20 uppercase, lowercase, and digit characters. Usually the passwords are between 100 and 120 bits of entropy. I try to use only letters and numbers because they are easier to type on mobile phones and other non-physical-keyboard-driven devices.
Post reply on HN