10-05-2020, 06:22 PM
I am trying to open a forgotten keystore password (jks).
My system:
Intel Core i5 4570
GeForce GTX 1060 3G
Win10
hashcat v6.1.1
GeForce drivers v.456.38
Cuda release 11.1, V11.1.74
========
I am using the command
The output is
I waited more than 24 hours and this is what I get when displaying the [s]tatus:
How can you speed up the process?
My benchmark
It seems to me that I am doing something wrong.
For some reason, the Intel HD 4600 integrated video card is loaded into the "Task Manager", but I need GeForce.
Picture in attachment
[attachment=761]
My system:
Intel Core i5 4570
GeForce GTX 1060 3G
Win10
hashcat v6.1.1
GeForce drivers v.456.38
Cuda release 11.1, V11.1.74
========
I am using the command
Code:
hashcat -m 15500 -a 3 hash.txt
Code:
hashcat (v6.1.1) starting...
* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #2: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
CUDA API (CUDA 11.1)
====================
* Device #1: GeForce GTX 1060 3GB, 2488/3072 MB, 9MCU
OpenCL API (OpenCL 1.2 CUDA 11.1.70) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: GeForce GTX 1060 3GB, skipped
OpenCL API (OpenCL 1.2 ) - Platform #2 [Intel(R) Corporation]
=============================================================
* Device #3: Intel(R) HD Graphics 4600, 1565/1629 MB (407 MB allocatable), 20MCU
* Device #4: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz, skipped
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Applicable optimizers applied:
* Zero-Byte
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
ATTENTION! Pure (unoptimized) backend kernels selected.
Using pure kernels enables cracking longer passwords but for the price of drastically reduced performance.
If you want to switch to optimized backend kernels, append -O to your commandline.
See the above message to find out about the exact limits.
Code:
Session..........: hashcat
Status...........: Running
Hash.Name........: JKS Java Key Store Private Keys (SHA1)
Hash.Target......: $jksprivk$*91ACDF5C34D988C88D68C7AE48B7A49A67A92026...4*key0
Time.Started.....: Mon Oct 05 18:25:05 2020 (25 secs)
Time.Estimated...: Mon Nov 20 09:43:44 2020 (45 days, 15 hours)
Guess.Mask.......: ?1?2?2?2?2?2?2?3?3?3 [10]
Guess.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined
Guess.Queue......: 10/15 (66.67%)
Speed.#1.........: 2310.1 MH/s (7.85ms) @ Accel:16 Loops:128 Thr:1024 Vec:1
Speed.#3.........: 48867.9 kH/s (5.94ms) @ Accel:128 Loops:32 Thr:8 Vec:1
Speed.#*.........: 2358.9 MH/s
Recovered........: 0/1 (0.00%) Digests
Progress.........: 59842166784/9301612953526272 (0.00%)
Rejected.........: 0/59842166784 (0.00%)
Restore.Point....: 83968/115760814336 (0.0%)
Restore.Sub.#1...: Salt:0 Amplifier:71680-71936 Iteration:0-256
Restore.Sub.#3...: Salt:0 Amplifier:40704-40736 Iteration:0-32
Candidates.#1....: lu5w8ptane -> hs9z80cker
Candidates.#3....: M1tyl2aner -> msbzaphane
Hardware.Mon.#1..: Temp: 69c Fan: 52% Util: 97% Core:1873MHz Mem:3802MHz Bus:16
Hardware.Mon.#3..: N/A
How can you speed up the process?
My benchmark
Code:
hashcat (v6.1.1) 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.
* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #2: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
CUDA API (CUDA 11.1)
====================
* Device #1: GeForce GTX 1060 3GB, 2488/3072 MB, 9MCU
OpenCL API (OpenCL 1.2 CUDA 11.1.70) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: GeForce GTX 1060 3GB, skipped
OpenCL API (OpenCL 1.2 ) - Platform #2 [Intel(R) Corporation]
=============================================================
* Device #3: Intel(R) HD Graphics 4600, 1565/1629 MB (407 MB allocatable), 20MCU
* Device #4: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz, skipped
Benchmark relevant options:
===========================
* --optimized-kernel-enable
Hashmode: 0 - MD5
Speed.#1.........: 12445.4 MH/s (48.13ms) @ Accel:64 Loops:1024 Thr:1024 Vec:8
Speed.#3.........: 220.0 MH/s (94.36ms) @ Accel:512 Loops:256 Thr:8 Vec:1
Speed.#*.........: 12665.4 MH/s
Hashmode: 100 - SHA1
Speed.#1.........: 4203.7 MH/s (71.44ms) @ Accel:32 Loops:1024 Thr:1024 Vec:1
Speed.#3.........: 84121.6 kH/s (61.32ms) @ Accel:128 Loops:256 Thr:8 Vec:1
Speed.#*.........: 4287.8 MH/s
It seems to me that I am doing something wrong.
For some reason, the Intel HD 4600 integrated video card is loaded into the "Task Manager", but I need GeForce.
Picture in attachment
[attachment=761]