Can anyone tell me where I can change my password on LinkedIn? I must be dense.
Assuming LinkedIn used SHA1 unsalted passwords and will continue to do so, and many of us do not want to delete our LinkedIn accounts, what should be the minimum number of characters we should use in our new password? 15? 20? 100? (I know, 100 is probably higher than they allow)
6.5 Million LinkedIn Password Hashes Leaked
481–490 of 547 posts
Re: 6.5 Million LinkedIn Password Hashes Leaked
#482Also note that according to other users, some of these hashes are at least 3 weeks old, they've had this list for some time.
Re: 6.5 Million LinkedIn Password Hashes Leaked
#483Earlier quoted context omitted.
Another data point: I changed my linkedin password about three weeks ago. The old one is in the list (already 00000-ed), the new one isn't.
Don't know if this adds anything, but both my old password (created eight years ago) and current password (changed six months ago) were on the list. Both were very unique - 20 characters mixed. Need to get better at changing my PWs every three months. It's really not that hard, just a matter of discipline.
Re: 6.5 Million LinkedIn Password Hashes Leaked
#484Re: 6.5 Million LinkedIn Password Hashes Leaked
#485Earlier 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…
A complete python script assuming you have hashes.txt in the same directory. http://dpaste.com/756007/
Re: 6.5 Million LinkedIn Password Hashes Leaked
#486Earlier quoted context omitted.
Some people actually do call names to others when face to face. Personally, while I don't, I do tend to get a little aggressive and then I'm often surprised with the backlash, because I get that way when I'm genuinely enjoying the conversation, not when I'm irritated.
Tone doesn't carry on the Internet, so no one knows you're enjoying it. Hence, it generally degrades the quality of the conversation, which is the opposite of what we want at HN.
Re: 6.5 Million LinkedIn Password Hashes Leaked
#487Re: 6.5 Million LinkedIn Password Hashes Leaked
#488http://arstechnica.com/security/2012/06/8-million-leaked-pas...
http://www.theregister.co.uk/2011/02/11/eharmony_data_breach...
Re: 6.5 Million LinkedIn Password Hashes Leaked
#489Some 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…
The hash of my password, set when I joined on October 10 2011, appears not to be in the list. Changed it anyway.
As you probably guessed from the fact that I posted my old password, I changed it just in case the list that was shared is only a partial list of what was obtained.
Re: 6.5 Million LinkedIn Password Hashes Leaked
#490Earlier quoted context omitted.
symmetric?
Each pipe stage reads from the left and writes to the right. The eye goes left to see the input and right to see the output if it's redirected to file. The input file is reliably the second word, so C-A M-f gets me to it if I want to operate on a different file. !!:1 gets me the file if I want to use it in a new command.
1. cat file
2. cat 3. echo abc|cat
4. echo abc|cat - file
cat can take input from the left, the right, or both
same goes for cut