Live data from Hacker News

6.5 Million LinkedIn Password Hashes Leaked

translate.google.com

541–547 of 547 posts

Re: 6.5 Million LinkedIn Password Hashes Leaked

#541

Some observations on this file: 0. This is a file of SHA1 hashes of short strings (i.e. passwords). 1. There are 3,521,180 hashes that begin with 00000. I believe that these represent hashes that the hackers have already broken and they have marked them with 00000 to indicate that fact. Evidence for this is that the SHA1 hash of 'password' does not appear in the list, but the same hash with the first five characters…

Nice observation dude, Can u please share the password file I dont have it anywhere. Thanks

Re: 6.5 Million LinkedIn Password Hashes Leaked

#543

Some observations on this file: 0. This is a file of SHA1 hashes of short strings (i.e. passwords). 1. There are 3,521,180 hashes that begin with 00000. I believe that these represent hashes that the hackers have already broken and they have marked them with 00000 to indicate that fact. Evidence for this is that the SHA1 hash of 'password' does not appear in the list, but the same hash with the first five characters…

replica" rel="nofollow">http://www.bestwatchsale.net>replica watches Watches Inc is known as the professional replica watches supplier, offer the high quality imitation watches from Rolex, Omega, Breitling,

Re: 6.5 Million LinkedIn Password Hashes Leaked

#544

Some observations on this file: 0. This is a file of SHA1 hashes of short strings (i.e. passwords). 1. There are 3,521,180 hashes that begin with 00000. I believe that these represent hashes that the hackers have already broken and they have marked them with 00000 to indicate that fact. Evidence for this is that the SHA1 hash of 'password' does not appear in the list, but the same hash with the first five characters…

For the security novices amongst us: I had no idea how to do this so I figured out a quick python script to test it: >>> from hashlib import sha1 >>> def check_pass(plaintext, offset=5): hashed = sha1(plaintext).hexdigest() return (hashed, '0' * offset + hashed[offset:]) >>> check_pass("linkedin") ('7728240c80b6bfd450849405e8500d6d207783b6', '0000040c80b6bfd450849405e8500d6d207783b6') Edit: I'm pretty sure JtR refers…

replica" rel="nofollow">http://www.bestwatchsale.net>replica watches Watches Inc is known as the professional replica watches supplier, offer the high quality imitation watches from Rolex, Omega, Breitling,

Re: 6.5 Million LinkedIn Password Hashes Leaked

#545

Earlier quoted context omitted.

For the security novices amongst us: I had no idea how to do this so I figured out a quick python script to test it: >>> from hashlib import sha1 >>> def check_pass(plaintext, offset=5): hashed = sha1(plaintext).hexdigest() return (hashed, '0' * offset + hashed[offset:]) >>> check_pass("linkedin") ('7728240c80b6bfd450849405e8500d6d207783b6', '0000040c80b6bfd450849405e8500d6d207783b6') Edit: I'm pretty sure JtR refers…

Obligatory perl one-liner: perl -MDigest::SHA -le '$h = substr( Digest::SHA::sha1_hex($ARGV[0]) , 5 ); open F, " )' password (for people without shells)

replica" rel="nofollow">http://www.bestwatchsale.net>replica watches Watches Inc is known as the professional replica watches supplier, offer the high quality imitation watches from Rolex, Omega, Breitling,

Re: 6.5 Million LinkedIn Password Hashes Leaked

#546

Earlier quoted context omitted.

For the security novices amongst us: I had no idea how to do this so I figured out a quick python script to test it: >>> from hashlib import sha1 >>> def check_pass(plaintext, offset=5): hashed = sha1(plaintext).hexdigest() return (hashed, '0' * offset + hashed[offset:]) >>> check_pass("linkedin") ('7728240c80b6bfd450849405e8500d6d207783b6', '0000040c80b6bfd450849405e8500d6d207783b6') Edit: I'm pretty sure JtR refers…

Obligatory perl one-liner: perl -MDigest::SHA -le '$h = substr( Digest::SHA::sha1_hex($ARGV[0]) , 5 ); open F, " )' password (for people without shells)

but stressed that “fundamentally, there are no differences replica" rel="nofollow">http://www.bestwatchsale.net>replica watches,” and ... Rich, profiled in a cover article for Harvard Magazine Replica Watches,

Re: 6.5 Million LinkedIn Password Hashes Leaked

#547
A salt may not have been enough to protect the passwords : if it is not complex enough, the presence of common passwords like "password" or "123456" make a brute-force attack on the salt itself possible in some case. I have performed a benchmark on that point in particular, and was able to retrieve a salt in five days, without strong optimization. A bit long to give all the numbers and code here, so the ref is http://gouigoux.com/blog/?p=46
Post reply on HN