06-20-2014, 03:30 PM
Unfortunately, cpu hashcat currently does not support custom charset that are that long.
Instead, oclHashcat can handle such custom charset "values".
Ofc, cpu hashcat should give a warning (or better it should support this too) instead of the exception.
It would be great if you could open a new trac ticket for this problem here: http://www.hashcat.net/trac/
Thx
Instead, oclHashcat can handle such custom charset "values".
Ofc, cpu hashcat should give a warning (or better it should support this too) instead of the exception.
It would be great if you could open a new trac ticket for this problem here: http://www.hashcat.net/trac/
Thx