09-30-2012, 11:05 PM
(09-30-2012, 10:28 PM)atom Wrote: Fast algorithms have an in-kernel rule engine. On there, if a rule leads to a situation that the password candidate is longer that 15 chars, it is -not- rejected and the test being done is unpredictable.
Shouldn't this be changed to warn that something not expected has happened?
Since I know my dictionaries and rules, I can inspect a run, and "know" that some should be run in the CPU hashcat, but I'm also having my Windows command (aka batch) files do some logging, so I can run a set of rules overnight, to have a record of what dictionaries and rules were run against which hash files.
Could the status screen show that the questionable state has happened, or something in he dictionary parsing/loading stage give a warning?