in theory you could just use the same command without the hash file and using --stdout to see all the password candidates.
e.g. if you had this command:
you could just use this command to "see" the candidates:
most of the time the output is very large and it's most of the time a waste to store the output to disk. It makes more sense to let hashcat try more clever non-overlapping attacks in the first place, without doing the rli2 based strategy (see hashcat-utils) of removing the already tested candidates.
e.g. if you had this command:
Code:
hashcat -m 14800 -r my.rules hash.txt dict.txt
you could just use this command to "see" the candidates:
Code:
hashcat --stdout -r my.rules dict.txt
most of the time the output is very large and it's most of the time a waste to store the output to disk. It makes more sense to let hashcat try more clever non-overlapping attacks in the first place, without doing the rli2 based strategy (see hashcat-utils) of removing the already tested candidates.