hashcat Forum

Full Version: New Oclhashcat with keepass - 0 speed
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello, 
the issue occurs on cracking speed, 
plz have look at this.
(this is after 4min of crecking)


oclHashcat>oclHashcat64.exe -m 13400 -d 1 -a 0 d:\hash d:\55 --weak-hash-threshold 0 -w 3
oclHashcat v2.01 (g67c1500) starting...

Device #1: Tahiti, 2112/3072 MB allocatable, 930Mhz, 28MCU

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c

Cache-hit dictionary stats d:\55: 36397290 bytes, 2158325 words, 2158325 keyspace

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

Session.Name...: oclHashcat
Status.........: Running
Input.Mode.....: File (d:\55)
Hash.Target....: $keepass$*2*15081984*222*03bb842d6f465847...
Hash.Type......: Keepass 1 (AES/Twofish) and Keepass 2 (AES)
Time.Started...: Sun Apr 10 12:08:09 2016 (4 mins, 47 secs)
[b]Speed.Dev.#1...:        0 H/s (102.24ms)[/b]
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 0/2158325 (0.00%)
Rejected.......: 0/0 (0.00%)
Restore.Point..: 0/2158325 (0.00%)
HWMon.GPU.#1...: 99% Util, 80c Temp, 15% Fan

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


I was trying to tune with -u and -n parametters without anny succes. Any1 can help?
15081984 iterations, wth!!

It's simply slower than 1H/s
(04-10-2016, 12:29 PM)atom Wrote: [ -> ]15081984 iterations, wth!!

It's simply slower than 1H/s


yeah... big number.. but on CPU i can crack this 2passwords  per second
KeeCracker.exe -w d:\55 ..\prv.kdbx

Rate: 0,3 per second    Last Candidate:

So I believe hash cat should be faster then cracking on cpu
Yeah, that's right. It's actually faster than 0H/s. Showing 0H/s is not the true speed. The best way to find out is to comment out this line:

Quote:if (rec_ms > SPEED_MAXAGE) continue;

and then you have to wait for the first update. This can take up to a day, depending on iteration count, -w setting and your GPU speed.