05-08-2018, 10:37 AM
I don't think this is a problem of hashcat, but this is how most command line tools work.
a dash is a special character and denotes the beginning of a command line parameter.
one dash introduces a short argument
two dashes introduce a long argument
Getopts (https://en.wikipedia.org/wiki/Getopts) for instance is kind of a defacto standard.
It's similar to a dollar sign ($) that is interpreted by your shell as a reference to a variable... or file globbing within your command.
There are slight differences of course, the shell intreprets the globbing and variable reference before hashcat even sees the final command, while getopts is used in terms of a library within the hashcat binary... but the "problem" and solutions are similar, you need to escape the special characters.
a dash is a special character and denotes the beginning of a command line parameter.
one dash introduces a short argument
two dashes introduce a long argument
Getopts (https://en.wikipedia.org/wiki/Getopts) for instance is kind of a defacto standard.
It's similar to a dollar sign ($) that is interpreted by your shell as a reference to a variable... or file globbing within your command.
There are slight differences of course, the shell intreprets the globbing and variable reference before hashcat even sees the final command, while getopts is used in terms of a library within the hashcat binary... but the "problem" and solutions are similar, you need to escape the special characters.