hashcat currently supports these attack modes:
-a 0 dict.txt
-a 1 dict1.txt dict2.txt
-a 3 ?a?a?a?a?a
-a 6 dict.txt ?a?a?a?a?a
-a 7 ?a?a?a?a?a dict.txt
you did use NONE (including the mask and/or dictionary parameters) of them, therefore hashcat defaults to the stdin mode which expects the password candidates from a pipe, something like this:
princeprocessor dict.txt | ./hashcat -r prince_optimized.rule hashes.txt
If hashcat doesn't receive any input from such a pipe, the speed will of course stay at 0 H/s and hashcat will "wait" for the first password candidates from the pipe (if you do not use a pipe it won't receive anything and speed will always stay at 0)
Please run: hashcat --help and read about the -a options available and how to use them.
-a 0 dict.txt
-a 1 dict1.txt dict2.txt
-a 3 ?a?a?a?a?a
-a 6 dict.txt ?a?a?a?a?a
-a 7 ?a?a?a?a?a dict.txt
you did use NONE (including the mask and/or dictionary parameters) of them, therefore hashcat defaults to the stdin mode which expects the password candidates from a pipe, something like this:
princeprocessor dict.txt | ./hashcat -r prince_optimized.rule hashes.txt
If hashcat doesn't receive any input from such a pipe, the speed will of course stay at 0 H/s and hashcat will "wait" for the first password candidates from the pipe (if you do not use a pipe it won't receive anything and speed will always stay at 0)
Please run: hashcat --help and read about the -a options available and how to use them.