Debug Mode - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Developer (https://hashcat.net/forum/forum-39.html) +--- Forum: hashcat (https://hashcat.net/forum/forum-40.html) +--- Thread: Debug Mode (/thread-5707.html) |
Debug Mode - ScAnMaG - 07-26-2016 You can do something like debug mode to show heshcat rule or mask that has worked for the hash? For example: Code: 554c6e5deae099ad8f637f2a646b9fe0:alone89inthedark | rule RE: Debug Mode - atom - 07-27-2016 You mean which mask matches a password? That's like impossible to answer, because there's too many. Do you want to know which rule cracked a password? Use debug mode. RE: Debug Mode - Kgx Pnqvhm - 07-27-2016 My practice is to use a logging method that writes to a log file, for every attack, the rule file or mask pattern being run. E.g., for a mask attack, one of the lines in my log file would be: Mask: ?u?l?l?l?l?d?d?d?d ; Notation: Aaaaa9999 ; Example: Bacon7215 And I have a way of notating the "found" file any results. RE: Debug Mode - atom - 08-12-2016 Hashcat uses markov-chain optimizations. IOW, there's no Aaaaa9999 (or better said Zzzzz9999) as final word. If you just want the mask which was used to crack your hash, why don't you name the output file not like the mask, then you can do the join from an outer script without overlapping. |