Defining character length. - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Support (https://hashcat.net/forum/forum-3.html) +--- Forum: hashcat (https://hashcat.net/forum/forum-45.html) +--- Thread: Defining character length. (/thread-8646.html) |
RE: Defining character length. - philsmd - 09-22-2019 just look it up here: https://hashcat.net/wiki/doku.php?id=rule_based_attack every rule that shortens the password, especially the "Truncate" rules "[" and "]" are able to generate passwords with "too short" length. Code: ] ] $s i.e. every rule that removes more than it adds for instance btw: you could also use stdin/pipe (hashcat --stdout -r rule dict.txt | hashcat -a 0 -m 2500 a.hccapx) or the -S (upper-case S) to get rid of every password candidate that doesn't fit the min. password length. The reason that this is not done when using other/normal commands (without pipe/-S) is for performance reasons, i.e. the kernel doesn't know the length before it is actually computed and (due to performance reasons) there is no further interaction between host and GPU/kernel when the GPU-based rule engine generates "too short" password candidates. Applying the rules is performed within the fast kernels too (except if you use -S) and therefore you can't easily reject them afterwards and pre-computing everything at the start could also be really slow depending on your dict/ruleset. RE: Defining character length. - Rdgeno - 09-22-2019 Thank you very much for taking the time to answer my question and explain it to me, that is very much appreciated. |