Bug with incremental and --restore?
#7
(04-03-2015, 06:26 PM)philsmd Wrote: You need to restore it, as such:
Code:
cudaHashcat64.exe --session x --restore

Yes i know, is not this the problem. I said that the --restore just skip a % of the process.
I give you some image example so you can understand.
In the image below i just started a random brute force and started to End-restore the process around 10 times (Q-restore-Q-restore-Q-restore.....)
It took about 20-30 seconds to do 10 times this thing and as you can see from the image, --restore skipped some things.

If is not clear:
- left image=start of the process
- right image= after 30 seconds (each Q-R skipped 2% in this case, around 1 minute each Q-R)

Recap: 10min = 30 seconds with Q-R

This is an example , but in the case of this morning , multiple Q-R skipped several more things , about 10% each time.
it is as if hashcat resume the process from a wrong point (a point not yet reached , A future or next char maybe ).

[Image: ZwbnY9s.png]


Messages In This Thread
Bug with incremental and --restore? - by giog7789 - 04-03-2015, 03:43 PM
RE: Bug with incremental and --restore? - by giog7789 - 04-03-2015, 09:30 PM