-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
Exhaustive password search #34
Comments
Hello, The recovery algorithm is roughly to bruteforce the first n-6 bytes of the password (with n being the password length) and then reconstruct the last 6 bytes if possible. The charset is used to bruteforce the first (n-6) bytes. The ending bytes can have values out of the charset. Could you confirm that the first n-6 bytes are alphanumeric characters? Otherwise, it would be a bug. |
I confirm that first n-6 bytes are alphanumeric characters. The recovered password does not work (but the found key work, I tested to extract a file with bkcrack command). I think this is because the password cannot be encoded in UTF-8 and so on when the unzip try to recompute the key, the key is wrong. password bytes -> string utf-8 -> password bytes does not give original bytes, so I don't think this is a problem of unicode characters in the password. Is there a way to get all other possibly passwords for this key to check if there is another one that can be converted to UTF-8? |
bkcrack does not test data integrity when deciphering or changing the password.
It is not implemented at the moment. I will hack something soon |
For the record, improvements to the password search algorithm are now available in version 1.6.0.
|
Hi,
I tried to recover a password from a key using the "-r 15 ?a" option, so I was expecting to only have a password with letters and numbers but the found password looks like to have strange characters:
Any idea what could be the problem?
Thanks!
The text was updated successfully, but these errors were encountered: