hashcat Forum - Error with estimated time

Hi Guys,

I have just tested the current github repo version of Hashcat and I noticed a minor error in the estimated time output.

It shows the estimated time to completion as being ~3 years, but the calculated time is stated as ~6 years.

./hashcat --version

v3.6.0-339-g1ed6576

Session..........: hashcat
Status...........: Running
Hash.Type........: DES (PT = $salt, key = $pass)
Hash.Target......:
Time.Started.....: Fri Aug 11 14:11:00 2017 (18 secs)
Time.Estimated...: Mon Oct 12 00:57:58 2020 (6 years, 58 days)
Guess.Mask.......: ?1?1?1?1?1?1?1?1 [8]
Guess.Charset....: -1 charsets/DES_full.charset, -2 Undefined, -3 Undefined, -4 Undefined
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 370.8 MH/s (65.69ms)
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 6618611712/72057594037927936 (0.00%)
Rejected.........: 0/6618611712 (0.00%)
Restore.Point....: 0/34359738368 (0.00%)
Candidates.#1....:
HWMon.Dev.#1.....: N/A

[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit =>

Cheers,
Matt

6 years looks good to me:

2^56/370000000/60/60/24/365 = 6.17

Yes, but the date itself is only 3 years from now: Mon Oct 12 00:57:58 2020

Hi Atom,

As epixoip said, 6 years is correct, however the "Time Estimated" is in the year 2020, which is only three years from now.

From Friday, Aug 11, 2017 until Monday, October 12, 2020 is only a little over 3 years.

Cheers,
Matt

@MattSR
Thanks for the report. It seems it was successfully fixed with the newest beta version (hashcat 3.6.0+367 or newer, https://hashcat.net/beta/).

See https://github.com/hashcat/hashcat/pull/1331

It would be great if you could test it and report back if the fix worked for you too.

BTW: please do not hesitate to create a github issue next time... if you are sure this is a bug/problem it might be better to report it on github because sometimes it could happen that not everything reported here is seen by a dev and fixed accordingly

Cheers @philsmd - I went to test it and run into another issue preventing -m 14000 from working, so I raised it as an issue in Github.

Thanks!

Just tested this now and it's fixed. Issue closed!