02-10-2012, 11:35 PM
Setting up custom charsets using -1 ABCDEF... works nice as long as you stick to the built-in charsets (http://hashcat.net/wiki/mask_attack), but if you want to go beyond that you'll have to put them on the command list after -1.
Attempting to attack CP437/CP850 charsets (see http://tbhost.eu/charset.txt, charsets used for Freerainbowtables), you're in for trouble because the command line (both Windows & Linux) will interpret certain characters as options or shell commands.
Expanding the list of built-in charsets could partially solve this, but since I'd like to test partial/full UTF-8/16 charsets, the command line with built-in charsets doesn't get flexible enough.
So my suggestion is to allow for putting custom charsets in textfiles.
(I'll openly admit that I rip of Bitweasils Multiforcer here, where he does exactly that with either single charset input (--charsetfile) or per-position charset file (--charsetfilemulti)
Attempting to attack CP437/CP850 charsets (see http://tbhost.eu/charset.txt, charsets used for Freerainbowtables), you're in for trouble because the command line (both Windows & Linux) will interpret certain characters as options or shell commands.
Expanding the list of built-in charsets could partially solve this, but since I'd like to test partial/full UTF-8/16 charsets, the command line with built-in charsets doesn't get flexible enough.
So my suggestion is to allow for putting custom charsets in textfiles.
(I'll openly admit that I rip of Bitweasils Multiforcer here, where he does exactly that with either single charset input (--charsetfile) or per-position charset file (--charsetfilemulti)