04-27-2020, 11:48 AM
Hi everyone,
I know that, using particular instructions (eg, <N) and options (eg, “-j), hashcat can reject a specific guess (ie, it does not compute the hash for it).
But, I was wondering, if there is some other intrinsic rejection rules automatically implied during the attack.
In particular, I would expect a guess to be rejected when the application of the mangling rule leaves the dictionary entry unchanged (with ':' as a special case). For instance: 'Password' + 'c' = 'Password'
Is this rejection mechanism employed from hashcat? Can/Should I force this behavior on a GPU-based attack?
Thanks.
I know that, using particular instructions (eg, <N) and options (eg, “-j), hashcat can reject a specific guess (ie, it does not compute the hash for it).
But, I was wondering, if there is some other intrinsic rejection rules automatically implied during the attack.
In particular, I would expect a guess to be rejected when the application of the mangling rule leaves the dictionary entry unchanged (with ':' as a special case). For instance: 'Password' + 'c' = 'Password'
Is this rejection mechanism employed from hashcat? Can/Should I force this behavior on a GPU-based attack?
Thanks.