Possible bug-no estimate if -a1 and -r

[Kgx Pnqvhm]

At the risk of having the moderators get after me for cross-posting, I'm asking here about a possible bug I mentioned in another thread.

Running hashcat-cli64.exe v0.41 using the Cain word list on some hashes with the -a 1 Combinator attack shows an estimated time after 0.03% upon reaching 0.04%:


Input.Mode: Dict (..\dicts\CainWordlist.txt)
Index.....: 1/1 (segment), 306706 (words), 3456292 (bytes)
Recovered.: 0/59 hashes, 0/50 salts
Speed/sec.: 34.95M plains, - words
Progress..: 96/306706 (0.03%)
Running...: 00:00:00:44
Estimated.: --:--:--:--

Input.Mode: Dict (..\dicts\CainWordlist.txt)
Index.....: 1/1 (segment), 306706 (words), 3456292 (bytes)
Recovered.: 0/59 hashes, 0/50 salts
Speed/sec.: 34.99M plains, 2 words
Progress..: 121/306706 (0.04%)
Running...: 00:00:00:56
Estimated.: 01:18:34:52

But if I have a rule via -r, (along with the -a 1), then even as of 0.05% it does not show an Estimated time. The AsIs.rule is simply ":".

Added rules from file AsIs.rule: 1

Input.Mode: Dict (..\dicts\CainWordlist.txt)
Index.....: 1/1 (segment), 306706 (words), 3456292 (bytes)
Recovered.: 0/59 hashes, 0/50 salts
Speed/sec.: 35.35M plains, - words
Progress..: 112/306706 (0.04%)
Running...: 00:00:03:26
Estimated.: --:--:--:--

Input.Mode: Dict (..\dicts\CainWordlist.txt)
Index.....: 1/1 (segment), 306706 (words), 3456292 (bytes)
Recovered.: 0/59 hashes, 0/50 salts
Speed/sec.: 35.36M plains, - words
Progress..: 144/306706 (0.05%)
Running...: 00:00:04:13
Estimated.: --:--:--:--

Is this a bug?

[M@LIK]

I suppose you are on Windows. Try with -r nul since you aren't using any actual rules.

[Kgx Pnqvhm]

I suppose you are on Windows. Try with -r nul since you aren't using any actual rules.

Added rules from file nul: 0

Input.Mode: Dict (..\dicts\CainWordlist.txt)
Index.....: 1/1 (segment), 306706 (words), 3456292 (bytes)
Recovered.: 0/59 hashes, 0/50 salts
Speed/sec.: 35.17M plains, - words
Progress..: 40/306706 (0.01%)
Running...: 00:00:00:19
Estimated.: --:--:--:--

Input.Mode: Dict (..\dicts\CainWordlist.txt)
Index.....: 1/1 (segment), 306706 (words), 3456292 (bytes)
Recovered.: 0/59 hashes, 0/50 salts
Speed/sec.: 35.19M plains, 2 words
Progress..: 104/306706 (0.03%)
Running...: 00:00:00:47
Estimated.: 01:18:35:01

[M@LIK]

Okay, I can't really explain why it doesn't print the time when using AsIs.rule, but if I were you I'd just modify my script in a way that if there's no rulefile set > use 'nul' as a rulefile and carry on.

[Kgx Pnqvhm]

What I'm trying to do is find out how much longer a specific rule makes a particular combinator attack.

I was trying a "do nothing" rule as a start.

[atom]

You need at least 100/X in your progress to have an ETC displayed

[Kgx Pnqvhm]

How does this apply to exactly the same operation being done, the first with only -a 1 running for less than a minute, getting to 0.04% and displaying an ETC, while with -r it goes for even 10 minutes, showing 0.013% but still no ETC?

Somehow having the -r involved changes how it determines when to show an ETC.

So, how far along should I wait to see an ETC for my -r example above?
(The -r for a rule file that just does nothing ":" takes 3x as long, but I waited 3x longer expecting to see an ETC.)

The next question is, of course, why the -r makes it take 3x as long, but I guess the overhead of just having a rule to apply slows the works down, I guess.

[atom]

Take the time it needs to inital display in -a 1 case and multiply it with the number of rules. That should work.

[Kgx Pnqvhm]

I'm still trying to understand why for the same attack, hashcat does give an ETC for:
Progress..: 121/306706 (0.04%)

Yet adding -r (for a rule that just does ":" so is functionally the same as no rule) gets even further percentagewise, yet doesn't give an ETC:
Progress..: 144/306706 (0.05%)

It seems like enough progress has been made to give an ETC, yet it doesn't give one.

I'm wondering if the -r somehow prevents hashcat from giving an ETC.

[atom]

You need at least (100 * nr-of-rules)/306706 in the progress to get an initial display.