-
Notifications
You must be signed in to change notification settings - Fork 9
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
sandgetpwdhash #2
Comments
-----BEGIN PGP SIGNED MESSAGE----- Hi Hubert, it's actually SHA1 with salt. for example if the pass would be "test" SHA1(testd1991455398e565a) = 867B4B7F6C7E5CCC50A1BD183D8C3E5801F20344 For Samsung however, the algorithm is slightly different. http://hashcat.net/forum/thread-2202.html The fastest way to crack it is using hashcat and gpu (samsung algo) :) Cheers, Am 22.01.2014 06:23, schrieb hubert3:
-----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJS37/cAAoJEKPg+vefL0V4hpAP+wS0cfId1XflWb8cnLI89KD5 |
Many thanks for the explanation and pointers. I made a python implementation here: https://gist.github.com/hubert3/8560499 Feel free to add this to the Sandy framework if it’s useful. |
For PIN 1234 set on my Samsung S4 4.2.2, sandgetpwdhash extracts the following:
867B4B7F6C7E5CCC50A1BD183D8C3E5801F20344:-3343618892075477414
How do I crack this? Is it a SHA1 hash? Does the salt not need to be converted to ascii hex?
I couldn't find any documentation of this in your talk slides or the sandy code.
Just checking before I do more work trying to work it out myself :)
The text was updated successfully, but these errors were encountered: