Hi,
I think I found a bug in hashcat v0.41 (32 and 64 bits). (oclhashcat-* are not impacted)
The problem is on the "?a" charset when used with a custom charset "?1".
?a means ?l?u?d?s = 95 characters.
3 tests :
I did *not* check with ?h/?D/?F/?R to see if also impacted.
The bug spreads : ?1?1 gives 4356 characters instead of 9025.
Thanks atom for your feedback.
I think I found a bug in hashcat v0.41 (32 and 64 bits). (oclhashcat-* are not impacted)
The problem is on the "?a" charset when used with a custom charset "?1".
?a means ?l?u?d?s = 95 characters.
3 tests :
Quote:hashcat-cli32.exe -a 3 hash.txt -1 ?l?u?d?s ?1Works OK (95).
Progress..: 95/95 (100.00%)
Quote:hashcat-cli32.exe -a 3 hash.txt ?aWorks OK (95).
Progress..: 95/95 (100.00%)
Quote:hashcat-cli32.exe -a 3 hash.txt -1 ?a ?1Only 66 characters are taken into account when using "?a" with custom charset "?1"
Progress..: 66/66 (100.00%)
I did *not* check with ?h/?D/?F/?R to see if also impacted.
The bug spreads : ?1?1 gives 4356 characters instead of 9025.
Thanks atom for your feedback.