metasploit-framework icon indicating copy to clipboard operation
metasploit-framework copied to clipboard

Cracker Enhancements

Open h00die opened this issue 2 years ago • 0 comments

To do list for myself

  1. Skip cracking attempts for hashes we don't have any. This happens because we build a list of ALL hashes the user wants to crack, but don't keep track of where they came from. This will save running things unnecessarily and save output
  2. If we haven't cracked something, we still output the cracked hashes table:
[*] Cracking lm hashes in wordlist mode...
[*]    Cracking Command: /usr/bin/hashcat --session=WOeLn8us --logfile-disable --potfile-path=/home/h00die/.msf4/john.pot --hash-type=3000 -O --attack-mode=0 /tmp/hashes_tmp20230108-873732-z0t372 /tmp/jtrtmp20230108-873732-xpap9
No hashes loaded.

No hashes loaded.

[+] Cracked Hashes
==============

 DB ID  Hash Type  Username  Cracked Password  Method
 -----  ---------  --------  ----------------  ------

[*] Checking nt hashes already cracked...

This is unnecessary and prints lots of things to the screen.

  1. hashcat was built on the assumption that it couldn't take usernames, which is untrue. There was a lot of logic built in to figure out which hash we cracked when we didn't have a username, this can all go in the bin

h00die avatar Jan 08 '23 16:01 h00die