Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
One thing they don't mention there is that already-cracked hashes in the dumps have the first five characters set to zero, so you have to check for that too.
One issue becomes apparent: about half the file has had the first 5 characters zeroed out. This is discussed at ycombinator. Atom has released a version of his Hashcat password cracker to deal with this. John-the-Ripper apparently also has published a patch for this.
...
So let's try the other file containing the corrupted hashes using the updated Hashcat feature on the other file, containing all the zeroed-out hashes.
As you can see, this straight dictionary lookup results in 688-thousand passwords being cracked, or about one fifth of all the zeroed hashes.
It gets worse when the guy starts using GPU processing. Worth a read.
One thing they don't mention there is that already-cracked hashes in the dumps have the first five characters set to zero, so you have to check for that too.
LinkedIn was using the SHA-1 digest for passwords, so the folks looking to reverse the passwords are using the following brute-force to match the posted hash:
echo -n "password" | openssl dgst -sha1
If you want to determine if your password was in one of the dumps, that's how. Match the SHA-1 hash that was generated from that sequence against one in the dump, and your password was in that dump.
...
And SHA-1 is intended to be fast to calculate; it's not a good general choice for hashing passwords.
And the GPU-based attacks are gonzo fast, based on the timestamps on some of the follow-up postings related to the original password dumps.
The security of your account is very important to us at LinkedIn. As a precaution, we disabled your password, and advise you to take the following steps to reset it. If you reset your password in the last two days, there is no need for further action.
1. Type www.linkedin.com/settings directly into your browser
2. Type in your email address and press Sign In, no password necessary
3. Follow the on-screen directions to reset your password
I think I will sign in and delete my account you ******* half witted protomonkeys.
Leave a comment: