02-28-2022, 05:34 PM
Hooray
I found this link
*ttp://registrationcenter-download.intel.com/akdlm/irc_nas/vcp/13794/opencl_runtime_18.1_x64_setup.msi
Now it takes only 11 seconds instead of 16 minutes.
Thank you.
I think thread name should be changed to
[Solved] why Hashcat v6.2.5 is slower than v5.1.0
I found this link
*ttp://registrationcenter-download.intel.com/akdlm/irc_nas/vcp/13794/opencl_runtime_18.1_x64_setup.msi
Now it takes only 11 seconds instead of 16 minutes.
Thank you.
Code:
C:\hashcat-6.2.5-207>hashcat.exe -I
hashcat (v6.2.5-207-gac1997027) starting in backend information mode
System Info:
============
OS.Name......: Windows
OS.Release...: N/A
HW.Platform..: N/A
HW.Model.....: N/A
OpenCL Info:
============
OpenCL Platform ID #1
Vendor..: Intel(R) Corporation
Name....: Intel(R) CPU Runtime for OpenCL(TM) Applications
Version.: OpenCL 2.1 WINDOWS
Backend Device ID #1
Type...........: CPU
Vendor.ID......: 8
Vendor.........: Intel(R) Corporation
Name...........: Intel(R) Celeron(R) CPU 1005M @ 1.90GHz
Version........: OpenCL 2.1 (Build 0)
Processor(s)...: 2
Clock..........: 1900
Memory.Total...: 16270 MB (limited to 2033 MB allocatable in one block)
Memory.Free....: 8103 MB
Local.Memory...: 32 KB
OpenCL.Version.: OpenCL C 2.0
Driver.Version.: 18.1.0.0920
Code:
C:\hashcat-6.2.5-207>hashcat.exe -D 1 -a 3 -m 22000 "WPA*01*ca5396d611cf330aebefd48ebbfb0e63*020000000001*020000000020*61703031***" "12345678"
hashcat (v6.2.5-207-gac1997027) starting
OpenCL API (OpenCL 2.1 WINDOWS) - Platform #1 [Intel(R) Corporation]
====================================================================
* Device #1: Intel(R) Celeron(R) CPU 1005M @ 1.90GHz, 8103/16270 MB (2033 MB allocatable), 2MCU
Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Optimizers applied:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
* Slow-Hash-SIMD-LOOP
Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.
Host memory required for this attack: 0 MB
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.
ca5396d611cf330aebefd48ebbfb0e63:020000000001:020000000020:ap01:12345678
Session..........: hashcat
Status...........: Cracked
Hash.Mode........: 22000 (WPA-PBKDF2-PMKID+EAPOL)
Hash.Target......: ca5396d611cf330aebefd48ebbfb0e63:020000000001:02000...0:ap01
Time.Started.....: Mon Feb 28 17:42:18 2022 (0 secs)
Time.Estimated...: Mon Feb 28 17:42:18 2022 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Mask.......: 12345678 [8]
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........: 171 H/s (1.34ms) @ Accel:32 Loops:1024 Thr:1 Vec:4
Recovered........: 1/1 (100.00%) Digests
Progress.........: 1/1 (100.00%)
Rejected.........: 0/1 (0.00%)
Restore.Point....: 0/1 (0.00%)
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:0-1
Candidate.Engine.: Device Generator
Candidates.#1....: 12345678 -> 12345678
Started: Mon Feb 28 17:42:10 2022
Stopped: Mon Feb 28 17:42:21 2022
I think thread name should be changed to
[Solved] why Hashcat v6.2.5 is slower than v5.1.0