04-27-2020, 12:00 PM
no, you shouldn't bother about this. It would be way too complex and time consuming (performance drop) to check this type of "rejection". It would cost MUCH more to check for a rejection than actually hash the password. It's not worth it.
However, you could in some specific cases optimize your word list and rule files to avoid some useless combinations.
Of course there could always be excpetions to this suggestion, but they are quite rare (for instance if the hash type is a very, very slow hash type like scrypt/bcrypt etc, but you would need to think about more clever approaches for these hash types anyway).
However, you could in some specific cases optimize your word list and rule files to avoid some useless combinations.
Of course there could always be excpetions to this suggestion, but they are quite rare (for instance if the hash type is a very, very slow hash type like scrypt/bcrypt etc, but you would need to think about more clever approaches for these hash types anyway).