+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Autotune never completes (/thread-10586.html)
Autotune never completes - bobcat - 01-18-2022
Hi all,
It seems like autotune runs forever on my laptop, never completing. I am running this:
Code:
hashcat -m 22000 -a 3 hashes ./weak.dicI made weak.dic with hcxpsktool, adding weak netgear candidates, and it's 3.7G in size.
Here's an example output:
Code:
The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework
Approaching final keyspace - workload adjusted.
Session..........: hashcat
Status...........: Exhausted
Hash.Mode........: 22000 (WPA-PBKDF2-PMKID+EAPOL)
Hash.Target......: hashes
Time.Started.....: Tue Jan 18 10:03:37 2022 (1 sec)
Time.Estimated...: Tue Jan 18 10:03:38 2022 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Mask.......: m5078b3ff8dc5 [13]
Guess.Queue......: 7565/308365585 (0.00%)
Speed.#1.........: 264 H/s (0.79ms) @ Accel:16 Loops:1024 Thr:1 Vec:4
Recovered........: 0/36 (0.00%) Digests, 0/23 (0.00%) Salts
Progress.........: 23/23 (100.00%)
Rejected.........: 0/23 (0.00%)
Restore.Point....: 1/1 (100.00%)
Restore.Sub.#1...: Salt:22 Amplifier:0-1 Iteration:0-1
Candidate.Engine.: Device Generator
Candidates.#1....: m5078b3ff8dc5 -> m5078b3ff8dc5
Hardware.Mon.SMC.: Fan0: 78%, Fan1: 78%
Hardware.Mon.#1..: Temp: 64c
Starting autotune. Please be patient...^Any ideas how to speed it up? Thanks!
RE: Autotune never completes - Chick3nman - 01-18-2022
Your command is incorrect. You should be using -a 0, not -a 3. This may not fix the issue fully but I suspect it is playing a major part.
RE: Autotune never completes - bobcat - 01-18-2022
(01-18-2022, 02:03 AM)Chick3nman Wrote: Your command is incorrect. You should be using -a 0, not -a 3. This may not fix the issue fully but I suspect it is playing a major part.
OMG I'm such an idiot, thanks!