Open BenKettlewell opened 5 years ago
Dang this might not be as quick of a fix as I initially thought. Either we'll have to 'know' that the user entered in a custom char set, or provide an option for the user to type in a char set with a new text field. Not sure what is the best solution.
I created a task with a custom mask mode.![image](https://user-images.githubusercontent.com/7477112/50717921-f6233f80-103f-11e9-9eb0-ffe240502516.png)
When I ran it against a known SHA1 hash it appeared to run successfully with the command below but failed to crack the hash and took only about 5 seconds so it's definitely not working. To validate I didn't have something else screwed up I removed the custom part and it cracked it instantly.
I believe the problem is formatting according to here.![image](https://user-images.githubusercontent.com/7477112/50717960-3a164480-1040-11e9-8484-f1391803826a.png)
I believe hashcat requires having the custom masks before the hash file.