08-11-2016, 12:47 PM
That is kind of obvious since --stdout doesn't expect any other other files besides the files needed for the attack type (e.g. -a 0 expects a dictionary or directory, -a 3 expects a mask, -a 1 expects 2 word lists etc).
--stdout does not need any hash file and if you use --stdout with a hash file it will be treated like a wordlist (because that is exactly what hashcat expects).
Also note there is no such thing like "full syntax" (there is only correct syntax/incorrect syntax ... and logical/semantic mistakes like you just made: i.e. specifying a .hccap file as a word list - because there is no need for .hccap files in --stdout mode -).
2. if you really want you can just pipe the modified/amplified plains into hashcat, e.g. hashcat --stdout -r a.rule b.dict | hashcat -m 2500 -w 3 ....
(ofc, the second command doesn't use --stdout)
short version is: --stdout is used to output all password candidates, it is not used to crack and therefore you do not use hash files, hash types etc
--stdout does not need any hash file and if you use --stdout with a hash file it will be treated like a wordlist (because that is exactly what hashcat expects).
Also note there is no such thing like "full syntax" (there is only correct syntax/incorrect syntax ... and logical/semantic mistakes like you just made: i.e. specifying a .hccap file as a word list - because there is no need for .hccap files in --stdout mode -).
2. if you really want you can just pipe the modified/amplified plains into hashcat, e.g. hashcat --stdout -r a.rule b.dict | hashcat -m 2500 -w 3 ....
(ofc, the second command doesn't use --stdout)
short version is: --stdout is used to output all password candidates, it is not used to crack and therefore you do not use hash files, hash types etc