You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a job is created with a pwdump formatted LM Hash (2 x 8 byte LM Hashes) which hashcat supports. When processed by the client the hash is automatically split by hashcat and cracked.
When hashtopolis receives the cracked hashes back, the hashes are not accepted as they are returned as two separate LM hashes (which they are) instead of the original pwdump joined up hash.
For example, the randomly generated dual LM D2C04F8696CB4C64EE3C66D0A47F10F8 which is HBOAIUJBMLUNBG
(Or seperately)
ee3c66d0a47f10f8:BMLUNBG
d2c04f8696cb4c64:HBOAIUJ
In the client output below you can see the hashtopolis client send back the cracked chunks but the web interface never reports the hash as being cracked.
I guess fix for this would be to split any inputted 16 byte LM hashes and store them as two 8 byte hashes.
Or support partial cracks so:
D2C04F8696CB4C64EE3C66D0A47F10F8 if only D2C04F8696CB4C64 is cracked then it would report: HBOAIUJ<UNCRACKED>
any progress on this? how are other people making the cracking of LM hashes easier? It would be awesome if you could input the whole password dump into Hashtopolis and it would let you handle both LM and NTLM hashes without additional processing.
zyronix
changed the title
Pwdump LM Hashes Incorrectly Handled
[ENHANCEMENT Pwdump LM Hashes Incorrectly Handled
Jun 16, 2023
any progress on this? how are other people making the cracking of LM hashes easier? It would be awesome if you could input the whole password dump into Hashtopolis and it would let you handle both LM and NTLM hashes without additional processing.
I have been using a bash script to split the hashes (cat ntds-lanman.txt | cut -d : -f3 | fold -w 16) then crack them and then using john the ripper to quickly reconstruct them. This feature would be really nice to have.
When a job is created with a pwdump formatted LM Hash (2 x 8 byte LM Hashes) which hashcat supports. When processed by the client the hash is automatically split by hashcat and cracked.
When hashtopolis receives the cracked hashes back, the hashes are not accepted as they are returned as two separate LM hashes (which they are) instead of the original pwdump joined up hash.
For example, the randomly generated dual LM D2C04F8696CB4C64EE3C66D0A47F10F8 which is HBOAIUJBMLUNBG
(Or seperately)
ee3c66d0a47f10f8:BMLUNBG
d2c04f8696cb4c64:HBOAIUJ
In the client output below you can see the hashtopolis client send back the cracked chunks but the web interface never reports the hash as being cracked.
I guess fix for this would be to split any inputted 16 byte LM hashes and store them as two 8 byte hashes.
Or support partial cracks so:
D2C04F8696CB4C64EE3C66D0A47F10F8 if only D2C04F8696CB4C64 is cracked then it would report:
HBOAIUJ<UNCRACKED>
On Client:
The text was updated successfully, but these errors were encountered: