7 ms·
fwiw, this could also be an elaborate hoax, given this facts. E.g. a list of simple password + combinations of the above simple password+"linkedin" variations.
by riffraff 14y ago
fwiw, this could also be an elaborate hoax, given this facts.
E.g. a list of simple password + combinations of the above simple password+"linkedin" variations.
- blantonl 14y agoI have a very unique strong password on LinkedIn, and it is on the list. Given that, this is no hoax.
- jaaron 14y agoSame here. Sucks too, because I liked that password.
- Yoms 14y agoMy complex unique password is also on this list (full hash no 5 0's). So nope, not a hoax. Unbelievable/insulting they didn't even bother to salt.
- jackalope 14y agoDo you remember when you first used this password at LinkedIn? It could help narrow the dates of the breach. Especially useful would be the presence of a strong password in the list that was subsequently changed. That might help determine its freshness, if the new password isn't present (although this may be an incomplete list from an ongoing breach).
- Yorn 14y agoI'm thinking this list is from closer to a year ago, I changed my password shortly after the MtGox hack last year and this hash is for my old password that was compromised during that time period.
- elektronaut 14y agoMy password is in the dump, and it was changed mid October 2010. I remember because I changed all my passwords when my laptop was stolen. The MtGox hack was in June 2011.
- Yoms 14y agoIt was about a year ago now. I checked the hashes for my previous password and it wasn't on the list... Mind you, as many have noticed, it seems to be very incomplete.
- deleted 14y ago[deleted]
- re_todd 14y agoYeah, even I, a newbie Rails programmer, going through the Agile Rails book learned how to salt. It isn't rocket science.
- jaaron 14y agoIt shouldn't just be a salt. It should be bcrypt.
- dudus 14y agoI couldn't find my password on the list and I've been using the same password for LinkedIn since I registered. I was trying to remember when was that. If someone know how to find out the last time you changed your pass or when you registered for linkedIn please let me know. I'd guess I use linkedIn for over 4 years at least.
- rodw 14y agoA "member since" date is available on the "Account & Settings" page. Choose "settings" in the drop down that appears when you hover over your (account) name in the upper right corner of any LinkedIn page.
- SkyMarshal 14y agoUnbelievable/insulting they used a general purpose, easily reversible hash like SHA1 in the first place. I would have thought everyone had seen the 'use bcrypt' page by now. http://codahale.com/how-to-safely-store-a-password/ http://codahale.com/how-to-safely-store-a-password/
- Nitramp 14y agoSince when is SHA1 easily reversible? Did I not get the memo? Salting should have been fine.
- eidorianu 14y agoI agree, I've tried several passwords and they match. If you're a Math person, please shed some light on the chances that this list covers the full space.
- cephalopod 14y ago6.5 million? Off the top of my head, assuming that passwords are only letters and 5 characters long this still wouldn't cover the possible space. [I think it's safe to ignore hash collisions] Are you trying passwords you've used on other sites, or random ones? If it's the former, then LI might not be the only source for the file.
- royce 14y agoI'm not a math person either, but here's some fodder for someone who is. Mark Burnett's extensive password collection (which he acknowledges is skewed, because it's largely based on cracked passwords, he only harvests passwords between 3 and 30 chars, etc.). Here's how some of his stats shake out: * Although my list contains about 6 million username/password combos, the list only contains about 1,300,000 unique passwords. * Of those, approximately 300,000 of those passwords are used by more than one person; about 1,000,000 only appear once (and a good portion of those are obviously generated by a computer). * The list of the top 20 passwords rarely changes and 1 out of every 50 people uses one of these passwords. So it's conceivable that 6M unique passwords could cover a very significant portion of a 120M user namespace. Ref: http://xato.net/passwords/how-i-collect-passwords http://xato.net/passwords/how-i-collect-passwords
- Terretta 14y agoIt's neat that the hashes are unique enough to serve as their own key. Obvious in retrospect, but still neat. Curious why some of the hashes have been obscured with 00000 but not all. It means more than one possible password could generate the remaining characters, but what does that help or protect?
- masterzora 14y ago0. There are known cases of peoples' passwords (including my own) not on the list.