When using a wordlist such as rockyou with the rule file rockyou-30000.rule, an error pops up:
ERROR: clEnqueueCopyBuffer() -30
Any way to get around it besides splitting the rule file to multiple, separate rule files?
Can not reproduce!
Quote:root@et:~/oclHashcat-1.34# ./oclHashcat64.bin /root/single /root/dict/untouched/rockyou.txt -r rules/rockyou-30000.rule -d 1
oclHashcat v1.34 starting...
Device #1: Tahiti, 3022MB, 1000Mhz, 32MCU
Device #2: skipped by user
Device #3: skipped by user
Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 30000
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Scalar-Mode
* Raw-Hash
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel ./kernels/4098/m00000_a0.Tahiti_1573.4_1573.4 (VM).kernel (509900 bytes)
Cache-hit dictionary stats /root/dict/untouched/rockyou.txt: 139921497 bytes, 14343296 words, 430298880000 keyspace
[s]tatus [p]ause [r]esume [b]ypass [q]uit => s
Session.Name...: oclHashcat
Status.........: Running
Rules.Type.....: File (rules/rockyou-30000.rule)
Input.Mode.....: File (/root/dict/untouched/rockyou.txt)
Hash.Target....: c919c165e21dce6dbc868377d1b10a39
Hash.Type......: MD5
Time.Started...: Sun Feb 22 23:08:09 2015 (1 sec)
Time.Estimated.: Sun Feb 22 23:10:33 2015 (2 mins, 22 secs)
Speed.GPU.#1...: 3134.3 MH/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 4831838208/430298880000 (1.12%)
Skipped........: 0/4831838208 (0.00%)
Rejected.......: 0/4831838208 (0.00%)
Restore.Point..: 0/14343296 (0.00%)
HWMon.GPU.#1...: 64% Util, 34c Temp, 25% Fan
Seems it happens more when I use --gpu-loops 4096 -n 32 it happens more, but I have seen it also without the gpu loops at some point.
C:\Users\Abe>C:\oclHashcat-1.33\oclHashcat64.exe -m 0 f2969362f9278742f94d3106db4d9f52 -r C:\oclHashcat-1.33\rules\rockyou-30000.rule F:\realuniq.lst --gpu-loops 4096 -n 32
oclHashcat v1.33 starting...
WARN: ADL_Overdrive6_FanSpeed_Get(): -1
Device #1: Hawaii, 3072MB, 1000Mhz, 44MCU
Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 30000
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Scalar-Mode
* Raw-Hash
Watchdog: Temperature abort trigger set to 95c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel C:\oclHashcat-1.33/kernels/4098/m00000_a0.Hawaii_1573.4_1573.4 (VM).kernel (508624 bytes)
Cache-hit dictionary stats F:\realuniq.lst: 15696118781 bytes, 1196843344 words, 35905300320000 keyspace
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
ERROR: clEnqueueCopyBuffer() -30
Wow 4k, I never tried that. Use 1k max
Yeah those -n/-u values don't really make sense. If you don't know what you're doing with those, just use ''-w 3'' instead.
Thanks atom, epixoip, I found those values while searching around this forum.
-w3 works fine, as well as --gpu-loops 1024 -n 32
Not sure what each of these does, not much documented on them either
The optimal -n/-u values vary depending on the algorithm. The -n/-u values you were using are for WPA, not MD5. Typically for MD5 you'd use -n 128 -u 1024 (or -n 256 if you have the RAM to support it.)
If you are unsure what the optimal values should be for each algorithm, just use ''-w 3'' as it will automatically select the optimal -n/-u values for that algorithm.