WPA Time.Estimated bug ?

[Mem5]

With oclHashcat-plus v0.13:

Code:

Session.Name...: oclHashcat-plus Status.........: Exhausted Input.Mode.....: File (C:\XX\XX\XX.dic) Hash.Target....: XXX(X <-> X) Hash.Type......: WPA/WPA2 Time.Started...: Thu Feb 07 20:20:01 2013 (5 mins, 46 secs) Time.Estimated.: Thu Feb 07 20:35:16 2013 (9 mins, 27 secs) Speed.GPU.#1...: 72068/s Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts Progress.......: 36738605/77063383 (47.67%) Rejected.......: 11845787/36738605 (32.24%) Started: Thu Feb 07 20:20:01 2013 Stopped: Thu Feb 07 20:25:49 2013

Say "Exhausted" but "Time.Estimated.: (9 mins, 27 secs)"

[epixoip]

it's because of how many were rejected (32.24%). the estimated time is based on how many *valid* combinations there are, but over 1/3 of your candidates were invalid, so it was able to finish way ahead of schedule.

[M@LIK]

I disagree, epixoip.
Notice the progress. The rejected are actually only rejected from the current progress.

Code:

Progress.......: 36738605/77063383 (47.67%) Rejected.......: 11845787/36738605 (32.24%)

2nd, progress always must be 100% when "Exhausted".
This is very fishy, gonna need the files to reproduce.