Bugs at new version
#1
Aside from the discussion of SL3, I guess the good way is to move on and try to fix as many bugs as possible on the lastest version available.

Do not read this message like I'm shouting or demanding a fixing. Just pointing minor errors.

First:

After installing a clean and fresh (drive sweeper+registry cleaning) installation of Cat 12.8, ocl-hashcat still points the message that you should use --force to continue. This isn't a problem since you can get rid of this, just typing the cmd said.

Second:

Session.Name...: oclHashcat-plus
Status.........: Exhausted
Rules.Type.....: File (D:\all.rule)
Input.Mode.....: File (D:\normal_found.txt)
Hash.Target....: File (D:\uncracked_2.txt)
Hash.Type......: SHA1
Time.Started...: Wed Jan 02 21:53:26 2013 (11 mins, 57 secs)
Time.Estimated.: > 10 Years
Speed.GPU.#1...: 162.0M/s
Recovered......: 20/1971163 Digests, 0/1 Salts
Progress.......: 104950214685/89998237287 (116.61%)
Rejected.......: 0/104950214685 (0.00%)
HWMon.GPU.#1...: 47% Util, 42c Temp, 32% Fan

Started: Wed Jan 02 21:53:26 2013
Stopped: Wed Jan 02 22:17:57 2013

This attack was going normally till it reaches the end. (look at the ECT and the progress). I'm not sure I can replicate this bug.

OS 7 X64
Cat 12.8
OCL v0.12

Thanks for the attention,
Regards.
#2
Yes, seen before.

As far as I can tell, this happens because of the dict caching thing. Try removing hashcat.dictstat and try again.
Btw, it's no big deal the attack will exhaust when its finished.
#3
I have the same issue but in linux, Using Mask attack, I'll try to replicate and post it, If I use for example 8 ?l oclhascat Do that in about 40 minutes, but with 9 ?l works about 20 seconds and mark > 10 years and stop working. In windows oclhashcat works better for me than in linux :S
#4
Using windows. Running mask attack. Every time i use --restore progress 0.00% and Time.Estimated.: 0 secs.
#5
(01-03-2013, 12:25 AM)User Wrote: First:

After installing a clean and fresh (drive sweeper+registry cleaning) installation of Cat 12.8, ocl-hashcat still points the message that you should use --force to continue. This isn't a problem since you can get rid of this, just typing the cmd said.

If hashcat says you dont have cat 12.8 installed then you dont have. You just think you have and thats one of the typical problem we face here again and again. Thats why I've added that strong check. The problem is that you have installed a later version than cat 12.8 before and driver sweeper can not uninstall them cleanly. You must use driver fusion or something recent and then reinstall cat 12.8. You will see it will work afterwards. Do not use --force