I think this is a problem of quotation marks "" vs ''
I think windows only accepts "" as quotation for parameters
The normal hashcat command is like this:
i.e. the options before the hash file and the mask after the hash file (but that's NOT the main problem over here).
The problem is how linux and windows differ when it comes to escaping and quoting of parameters.
I would try with two " instead of two ' or even try (for testing purposes) with a smaller custom charset with e.g. just ?d
for testing:
if this works with just ?d as first custom charset, you will easily figure out how to add further character (or character sets) to -1, just by testing it.
That said, yeah the command looks quite good, but escaping/quoting rules are sometimes not the same across different operating systems.
I think windows only accepts "" as quotation for parameters
The normal hashcat command is like this:
Code:
hashcat64.exe -m 14800 -a 3 -1 "?d!@$&" -2 ?u?1 manifest.txt ?2?1?1?1?1?1i.e. the options before the hash file and the mask after the hash file (but that's NOT the main problem over here).
The problem is how linux and windows differ when it comes to escaping and quoting of parameters.
I would try with two " instead of two ' or even try (for testing purposes) with a smaller custom charset with e.g. just ?d
for testing:
Code:
hashcat64.exe -m 14800 -a 3 -1 ?d -2 ?u?1 manifest.txt ?2?1?1?1?1?1if this works with just ?d as first custom charset, you will easily figure out how to add further character (or character sets) to -1, just by testing it.
That said, yeah the command looks quite good, but escaping/quoting rules are sometimes not the same across different operating systems.