osx 10.13.1 speed issue

[johnjohnsp1]

Hello,

I'm running latest release of hash cat direct from git repository:
v.4.0.1-10-gea5425b3
then issued the git submodule update --init for the OpenCL and as last I did a test:

./hashcat -b -m1000
hashcat (v4.0.1-10-gea5425b3) starting in benchmark mode...

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

OpenCL Platform #1: Apple
=========================
* Device #1: Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz, skipped.
* Device #2: HD Graphics 4000, 384/1536 MB allocatable, 16MCU
* Device #3: GeForce GT 650M, 256/1024 MB allocatable, 2MCU

Benchmark relevant options:
===========================
* --optimized-kernel-enable

Hashmode: 1000 - NTLM

Speed.Dev.#2.....:   334.9 MH/s (49.58ms)
Speed.Dev.#3.....:   560.5 MH/s (67.98ms)
Speed.Dev.#*.....:   895.4 MH/s

Started: Mon Nov 13 18:32:55 2017
Stopped: Mon Nov 13 18:33:03 2017

the problem is when I try to crack a single hash where the speed become extremely slow, like this:

./hashcat -a0 -m1000 44d3b96ae559418e8d36264198b60112 ../hashcat400/rockyou.txt -r rules/best64.rule

hashcat (v4.0.1-10-gea5425b3) starting...

OpenCL Platform #1: Apple
=========================
* Device #1: Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz, skipped.
* Device #2: HD Graphics 4000, 384/1536 MB allocatable, 16MCU
* Device #3: GeForce GT 650M, 256/1024 MB allocatable, 2MCU

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 77

Applicable optimizers:
* Zero-Byte
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Raw-Hash

Password length minimum: 0
Password length maximum: 256

ATTENTION! Pure (unoptimized) OpenCL kernels selected.
This enables cracking passwords and salts > length 32 but for the price of drastical reduced performance.
If you want to switch to optimized OpenCL kernels, append -O to your commandline.

Watchdog: Temperature abort trigger disabled.
Watchdog: Temperature retain trigger disabled.

Dictionary cache hit:
* Filename..: ../hashcat400/rockyou.txt
* Passwords.: 14344385
* Bytes.....: 139921507
* Keyspace..: 1104517645

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

Session..........: hashcat
Status...........: Running
Hash.Type........: NTLM
Hash.Target......: 44d3b96ae559418e8d36264198b60112
Time.Started.....: Mon Nov 13 18:42:39 2017 (4 secs)
Time.Estimated...: Mon Nov 13 18:46:18 2017 (3 mins, 35 secs)
Guess.Base.......: File (../hashcat400/rockyou.txt)
Guess.Mod........: Rules (rules/best64.rule)
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....:  4192.0 kH/s (6.23ms)
Speed.Dev.#3.....:   844.2 kH/s (3.86ms)
Speed.Dev.#*.....:  5049.7 kH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 21000704/1104517645 (1.90%)
Rejected.........: 0/21000704 (0.00%)
Restore.Point....: 269824/14344385 (1.88%)
Candidates.#2....: greatdanes13 -> duke123
Candidates.#3....: herman -> 

anyone else noticed this ?

thanks

[Chick3nman]

Read the warning message in your output:

ATTENTION! Pure (unoptimized) OpenCL kernels selected.
This enables cracking passwords and salts > length 32 but for the price of drastical reduced performance.
If you want to switch to optimized OpenCL kernels, append -O to your commandline.

[johnjohnsp1]

I did another run with -O to my command line but results are far away from the benchmark:

./hashcat -a0 -m1000 44d3b96ae559418e8d36264198b60112 ../hashcat400/rockyou.txt -r rules/best64.rule -O
hashcat (v4.0.1-10-gea5425b3) starting...

OpenCL Platform #1: Apple
=========================
* Device #1: Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz, skipped.
* Device #2: HD Graphics 4000, 384/1536 MB allocatable, 16MCU
* Device #3: GeForce GT 650M, 256/1024 MB allocatable, 2MCU

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 77

Applicable optimizers:
* Optimized-Kernel
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Raw-Hash

Password length minimum: 0
Password length maximum: 27

Watchdog: Temperature abort trigger disabled.
Watchdog: Temperature retain trigger disabled.

Dictionary cache hit:
* Filename..: ../hashcat400/rockyou.txt
* Passwords.: 14344385
* Bytes.....: 139921507
* Keyspace..: 1104517645

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

Session..........: hashcat
Status...........: Running
Hash.Type........: NTLM
Hash.Target......: 44d3b96ae559418e8d36264198b60112
Time.Started.....: Mon Nov 13 19:04:44 2017 (4 secs)
Time.Estimated...: Mon Nov 13 19:04:58 2017 (10 secs)
Guess.Base.......: File (../hashcat400/rockyou.txt)
Guess.Mod........: Rules (rules/best64.rule)
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....: 59537.3 kH/s (6.01ms)
Speed.Dev.#3.....: 18069.2 kH/s (12.17ms)
Speed.Dev.#*.....: 77579.9 kH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 307343113/1104517645 (27.83%)
Rejected.........: 151305/307343113 (0.05%)
Restore.Point....: 3975074/14344385 (27.71%)
Candidates.#2....: sara4321 -> anrean
Candidates.#3....: sarahpham -> ara4ar

anything else to try ?

[Chick3nman]

That looks about like what I would expect. Try the following command line and see if it give you the same speed as the benchmark:

./hashcat -a3 -m1000 44d3b96ae559418e8d36264198b60112 ?a?a?a?a?a?a?a?a -O


Bruteforce/Mask attacks are what the benchmark is comparable to. Wordlists and rules, especially small lists with small rules like the ones you loaded, will tend to be much slow as the GPUs are starved for work.

[johnjohnsp1]

did the test you told and seems working much closer to the benchmark speed:

./hashcat -a3 -m1000 44d3b96ae559418e8d36264198b60112 ?a?a?a?a?a?a?a?a -O
hashcat (v4.0.1-10-gea5425b3) starting...

OpenCL Platform #1: Apple
=========================
* Device #1: Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz, skipped.
* Device #2: HD Graphics 4000, 384/1536 MB allocatable, 16MCU
* Device #3: GeForce GT 650M, 256/1024 MB allocatable, 2MCU

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:
* Optimized-Kernel
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash

Password length minimum: 0
Password length maximum: 27

Watchdog: Temperature abort trigger disabled.
Watchdog: Temperature retain trigger disabled.

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

Session..........: hashcat
Status...........: Running
Hash.Type........: NTLM
Hash.Target......: 44d3b96ae559418e8d36264198b60112
Time.Started.....: Tue Nov 14 05:35:47 2017 (2 secs)
Time.Estimated...: Thu Apr 26 20:10:51 2018 (163 days, 13 hours)
Guess.Mask.......: ?a?a?a?a?a?a?a?a [8]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....: 277.0 MH/s (6.40ms)
Speed.Dev.#3.....: 192.4 MH/s (4.21ms)
Speed.Dev.#*.....: 469.4 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 1320239104/6634204312890625 (0.00%)
Rejected.........: 0/1320239104 (0.00%)
Restore.Point....: 0/735091890625 (0.00%)
Candidates.#2....: M@h@0 -> (A@.2
Candidates.#3....: wuTm! -> Auw')

thanks for the hint, I was wondering if I was missing something to the compile options.
Usually within old version of hashcat I did have no problems using rocky as wordlist with a speed like bench.

thanks again.