Thanks for your reply.
I think most people would agree that this is clearly a "workaround" rather than a solution. 99% of users would not know about this workaround, and would expect hashcat to work differently.
I strongly suggest to have hashcat reject passwords *only* after it goes through the rule file. This is the expected behavior, even if it means that hashcat would run slightly slower, at least it wont reject 50% of a password list and many rules when it does not have to just yet (as far as WPA or other hash functions)
It is scary to think that a hash can be cracked but hashcat is not finding it within its own password list and rule file.
I think most people would agree that this is clearly a "workaround" rather than a solution. 99% of users would not know about this workaround, and would expect hashcat to work differently.
I strongly suggest to have hashcat reject passwords *only* after it goes through the rule file. This is the expected behavior, even if it means that hashcat would run slightly slower, at least it wont reject 50% of a password list and many rules when it does not have to just yet (as far as WPA or other hash functions)
It is scary to think that a hash can be cracked but hashcat is not finding it within its own password list and rule file.