truncating passwords instead of rejecting them
#2
see https://hashcat.net/wiki/doku.php?id=rule_based_attack

There is a rule to truncate password candidates:
Truncate @ N 'N Truncate word at position N

If you wish you could also use the "multi rule" feature, see https://hashcat.net/wiki/doku.php?id=rul...ulti-rules
This allows you to use oclHashcat as follows:
-r my_normal_rule_file.rule -r truncate_at_8.rule

Hence, you don't need to add the "truncation rule" on each line, nor do you need to (quote) "maintain separate rule sets for various lengths"

Truncating instead of rejecting wouldn't make much sense in general (for specific hash types with limit), and keeping track of which (truncated) plains were already checked even less sense (too much memory consumption, not working for plains modified on the GPU by rules etc).

If I am not completely mistaken, whenever the plain was not rejected when loading it, for many hash types who have some limit (maximum password length) the plain will be kind of automatically truncated anyway if it makes it that far (already modified plain, rule etc, loaded on GPU ).


Messages In This Thread
RE: truncating passwords instead of rejecting them - by philsmd - 01-14-2015, 09:42 PM