The syntax is explained here:
https://hashcat.net/wiki/?id=mask_attack...mask_files
(and also within the FAQ: https://hashcat.net/wiki/doku.php?id=fre..._mask_file)
#1 if you want to use a custom charset without spaces, just use something like this:
#2 the custom charsets must be defined within the .hcmask file for each line that uses custom charsets (remember: previous versions of hashcat did have this "feature" to be able to use the custom charset defined on the command line and/or the default custom charsets, but users were utterly confused about this... whenever they forgot to set the correct custom charset within the line, they reported problems with "unexpected" behaviour... "hashcat doesn't work correctly, it uses the wrong mask". The way it currently is, it will give you a clear error message that you should tell hashcat what custom charsets you want to use for each mask).
https://hashcat.net/wiki/?id=mask_attack...mask_files
(and also within the FAQ: https://hashcat.net/wiki/doku.php?id=fre..._mask_file)
#1 if you want to use a custom charset without spaces, just use something like this:
Quote:!"#$%&'()*+\,-./:;<=>?@[\]^_`{|}~,?a?a?a?a?1where !"#$%&'()*+,-./:;<=>?@[\]^_`{|}~ is defined as your custom charset 1 (-1 or --custom-charset1) and ?a?a?a?a?1 is your mask (which is using ?1)
#2 the custom charsets must be defined within the .hcmask file for each line that uses custom charsets (remember: previous versions of hashcat did have this "feature" to be able to use the custom charset defined on the command line and/or the default custom charsets, but users were utterly confused about this... whenever they forgot to set the correct custom charset within the line, they reported problems with "unexpected" behaviour... "hashcat doesn't work correctly, it uses the wrong mask". The way it currently is, it will give you a clear error message that you should tell hashcat what custom charsets you want to use for each mask).