-
Notifications
You must be signed in to change notification settings - Fork 245
Task Creation Guidelines
#General
Task generation is one of the most difficult parts of hashtopussy and can make the difference between a smooth experience and a terrible one. This section will be the "best practices" that you should follow. The formatting used here is not a requirement but if you are having issues with a particular task try changing it to the format found here. Remember some OS's are case sensitive even if you don't have a Unix machine now you may in the future.
NEVER use client specific parameters in your tasks:
--gpu-temp-disable``--gpu-temp-retain``--opencl-devices should be placed into client the client specific "Extra parameters" field. This can be configured in agents.php then click on agent name
Below is the correct format you should be using when entering tasks into hashtopussy.
Example: -a0 #HL# Wordlist.txt
Example -a0 #HL# Wordlist.txt -r Rules.rule
You can stack rule files with hashcat -r Rules.rule -r Rules2.rule
Example: -a1 #HL# Wordlist.Left Wordlist.Right
Example: -a3 #HL# ?a?a?a?a?a?a
Example: -a3 #HL# -1 Custom.hcchar ?1?1?1?1?1?1
Custom character files can and should be specified especially when dealing with special characters in masks. Simply place the characters you wish to run into a txt document and place the file into your command like any other wordlist. Be sure you specify the custom mask option (-1,-2,-3,-4) before the hcchar file. This prevents nasty command line confusion with special/escape characters.
Example:-a6 #HL# Wordlist.txt ?a?a?a?a?a?a
Example:-a7 #HL# ?a?a?a?a?a?a Wordlist.txt
Example:-a7 #HL# -1 Custom.hcchar ?1?1?1?1 Wordlist.txt
Be mindful of the ordering of wordlist and mask. hashcat requires the ordering to match the mode you are running. Please see Brute-force section for Custom.hcchar explanation.