Wpa Brute Force Attack Stuck At The End
#1
Hi,

I'm using a bruteforce attack to crack a wpa hash, at around 99.60% completion rate it shows the message: Approaching final keyspace, workload ajusted. Then it stays stuck at 22 secs remaining, and won't progress any further.
These are the parameters I use to launch it:
Code:
hashcat64.exe -m 2500 -a3 wpa.hccap ?d?d?d?d?d?d?d?d --powertune-enable --gpu-temp-abort=100 --gpu-temp-retain=89 --gpu-temp-disable --nvidia-spin-damp=50 -o words.txt

This is the output:
Quote:C:\Users\arthu\Desktop\hashcat-3.10>hashcat64.exe -m 2500 -a3 wpa.hccap ?d?d?d?d?d?d?d?d --powertune-enable --gpu-temp-abort=100 --gpu-temp-retain=89 --gpu-temp-disable --nvidia-spin-damp=50 -o words.txt
                 hashcat (v3.10) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
- Device #1: Intel(R) HD Graphics 4400, 480/1921 MB allocatable, 20MCU
- Device #2: Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz, skipped

OpenCL Platform #2: NVIDIA Corporation
======================================
- Device #3: GeForce GT 740M, 512/2048 MB allocatable, 2MCU
- Device #3: WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702
             See the wiki on how to disable it: https://hashcat.net/wiki/doku.php?id=timeout_patch

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
* Slow-Hash-SIMD
Watchdog: Temperature abort trigger disabled
Watchdog: Temperature retain trigger disabled

INFO: approaching final keyspace, workload adjusted

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

Session.Name...: hashcat
Status.........: Running
Input.Mode.....: Mask (?d?d?d?d?d?d?d?d) [8]
Hash.Target....: IFSP_prof (c0:c1:c0:7f:cf:99 <-> a4:5d:36:c2:53:2a)
Hash.Type......: WPA/WPA2
Time.Started...: Thu Sep 29 06:44:21 2016 (14 secs)
Time.Estimated.: Thu Sep 29 06:45:30 2016 (25 secs)
Speed.Dev.#1...:        0 H/s (0.00ms)
Speed.Dev.#3...:    14413 H/s (18.05ms)
Speed.Dev.#*...:    14413 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 99636360/100000000 (99.64%)
Rejected.......: 0/99636360 (0.00%)
Restore.Point..: 9960000/10000000 (99.60%)

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



Session.Name...: hashcat
Status.........: Running
Input.Mode.....: Mask (?d?d?d?d?d?d?d?d) [8]
Hash.Target....: IFSP_prof (c0:c1:c0:7f:cf:99 <-> a4:5d:36:c2:53:2a)
Hash.Type......: WPA/WPA2
Time.Started...: Thu Sep 29 06:44:21 2016 (21 mins, 4 secs)
Time.Estimated.: Thu Sep 29 07:06:19 2016 (25 secs)
Speed.Dev.#1...:        0 H/s (0.00ms)
Speed.Dev.#3...:    14413 H/s (18.05ms)
Speed.Dev.#*...:    14413 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 99636360/100000000 (99.64%)
Rejected.......: 0/99636360 (0.00%)
Restore.Point..: 9960000/10000000 (99.60%)

[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit =>
#2
pssst apply the timeout patch...
#3
timeout patch? Can you be more specific?
EDIT:
Found it, I'm going to try that.