Attack PMKID 16800 is slow
#1
After I read this thread https://hashcat.net/forum/thread-7717.html, I tried the attack 16800, I have latest version of hashcat git pull few minutes ago, but attack 16800 is slow.
My GPU is not very fast, but I exptect a more fast execution.

Code:
hashcat (v4.2.1-4-g188a9568) 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: Advanced Micro Devices, Inc.
================================================
* Device #1: Iceland, 3263/4080 MB allocatable, 6MCU

OpenCL Platform #2: Intel(R) Corporation
========================================
* Device #2: Intel(R) Gen9 HD Graphics NEO, 3060/6120 MB allocatable, 24MCU

OpenCL Platform #3: Intel(R) Corporation
========================================
* Device #3: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 1912/7650 MB allocatable, 8MCU

Benchmark relevant options:
===========================
* --force
* --opencl-device-types=1,2
* --optimized-kernel-enable

Hashmode: 16800 - WPA-PMKID-PBKDF2 (Iterations: 4096)

Speed.Dev.#1.....:    27710 H/s (54.29ms) @ Accel:128 Loops:32 Thr:256 Vec:1
Speed.Dev.#2.....:     7789 H/s (95.69ms) @ Accel:32 Loops:16 Thr:256 Vec:1
Speed.Dev.#3.....:     7747 H/s (63.92ms) @ Accel:512 Loops:512 Thr:1 Vec:8
Speed.Dev.#*.....:    43246 H/s

Started: Sun Aug 12 12:14:24 2018
Stopped: Sun Aug 12 12:14:36 2018

This is the speed with MD5
Code:
hashcat (v4.2.1-4-g188a9568) 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: Advanced Micro Devices, Inc.
================================================
* Device #1: Iceland, 3263/4080 MB allocatable, 6MCU

OpenCL Platform #2: Intel(R) Corporation
========================================
* Device #2: Intel(R) Gen9 HD Graphics NEO, 3060/6120 MB allocatable, 24MCU

OpenCL Platform #3: Intel(R) Corporation
========================================
* Device #3: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 1912/7650 MB allocatable, 8MCU

Benchmark relevant options:
===========================
* --force
* --opencl-device-types=1,2
* --optimized-kernel-enable

Hashmode: 0 - MD5

Speed.Dev.#1.....:  1601.5 MH/s (61.89ms) @ Accel:512 Loops:128 Thr:256 Vec:1
Speed.Dev.#2.....:   407.6 MH/s (120.75ms) @ Accel:128 Loops:64 Thr:256 Vec:4
Speed.Dev.#3.....:   437.1 MH/s (18.93ms) @ Accel:1024 Loops:1024 Thr:1 Vec:8
Speed.Dev.#*.....:  2446.2 MH/s

Started: Sun Aug 12 12:34:43 2018
Stopped: Sun Aug 12 12:34:54 2018


This is the speed with attack 2500 WPA-EAPOL-PBKDF2
Code:
hashcat (v4.2.1-4-g188a9568) 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: Advanced Micro Devices, Inc.
================================================
* Device #1: Iceland, 3263/4080 MB allocatable, 6MCU

OpenCL Platform #2: Intel(R) Corporation
========================================
* Device #2: Intel(R) Gen9 HD Graphics NEO, 3060/6120 MB allocatable, 24MCU

OpenCL Platform #3: Intel(R) Corporation
========================================
* Device #3: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 1912/7650 MB allocatable, 8MCU

Benchmark relevant options:
===========================
* --force
* --opencl-device-types=1,2
* --optimized-kernel-enable

Hashmode: 2500 - WPA-EAPOL-PBKDF2 (Iterations: 4096)

Speed.Dev.#1.....:    26041 H/s (54.29ms) @ Accel:128 Loops:32 Thr:256 Vec:1
Speed.Dev.#2.....:     7740 H/s (95.90ms) @ Accel:32 Loops:16 Thr:256 Vec:1
Speed.Dev.#3.....:     7613 H/s (65.29ms) @ Accel:512 Loops:512 Thr:1 Vec:8
Speed.Dev.#*.....:    41394 H/s

Started: Sun Aug 12 12:40:29 2018
Stopped: Sun Aug 12 12:40:58 2018

Is it a normal speed of something is wrong?
Reply
#2
That's what you can expect from mid range mobile hardware. Especially the md5/wpa ratio is absolutely normal.
Reply
#3
It is still doing the same computation as mode 2500... AKA it still has to calculate the PMK which is very slow.
Reply