In this 2011 thread:
http://hashcat.net/forum/thread-698.html
... someone asked about "wordlist clipping" - being able to truncate passwords instead of rejecting them.
The suggestion at the time was to modify all rules to truncate words. Is this still the best answer?
When working large collection of rules, it would be very convenient to not have to maintain separate rule sets for various lengths of password, and keep both truncated and non-truncated rules in sync.
Ideally, it would be great if oclhashcat could recognize the maximum possible word length of the target hash format, and automatically truncate rather than rejecting (unless it results in a duplicate password). This is what JtR does, IIRC.
This would be especially handy for DES crypt.
http://hashcat.net/forum/thread-698.html
... someone asked about "wordlist clipping" - being able to truncate passwords instead of rejecting them.
The suggestion at the time was to modify all rules to truncate words. Is this still the best answer?
When working large collection of rules, it would be very convenient to not have to maintain separate rule sets for various lengths of password, and keep both truncated and non-truncated rules in sync.
Ideally, it would be great if oclhashcat could recognize the maximum possible word length of the target hash format, and automatically truncate rather than rejecting (unless it results in a duplicate password). This is what JtR does, IIRC.
This would be especially handy for DES crypt.