-
Notifications
You must be signed in to change notification settings - Fork 679
-
Notifications
You must be signed in to change notification settings - Fork 679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passwd Hash Length - Blockchain.info #55
Comments
I'm afraid I don't understand.... A Blockchain,info wallet file doesn't contain the hash of the main password. The only way to check if the main password is correct is to attempt to decrypt the wallet file using the main password, and see if the result looks like JSON plaintext. Once decrypted, the JSON plaintext does contain the hash of the second password (it's called the |
Sorry, please disregard the question. I was trying to brute force the second password, and wondered if the hash of the second password obtained via the extract scripts gave me any clue about possible password length. Thank you for your time. |
I definitely misunderstood, but now I understand what you were asking. Although you don't need the answer any longer, just for the record it's "no", there's no way to deduce the password length from any of the data retrieved by the various extract scripts. |
Sorry if this isn't the right place- I have the first password, 2fa, and the second password hash. Trying to use hashcat to undo the hash with these: 1400 | SHA-256 | Raw Hash Just wondering if this is even possible or if I'm wasting my time here. Feels like I'm really close to cracking it but it's too long of a password for me to bruteforce locally. |
Suppose I have both the hashes for my main password and my second password for a blockchain.info wallet. Do the lengths of the hashes indicate whether one password is possibly longer than the other? Currently the 2nd hash is longer than the 1st. Thoughts?
The text was updated successfully, but these errors were encountered: