hashcat Forum
dcc2 not work on optimized kernel - Printable Version

+- 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: dcc2 not work on optimized kernel (/thread-11272.html)

dcc2 not work on optimized kernel - MidnightHunter - 01-26-2023

Hi everyone

I couldn't launch cracking dcc2 with optimized kernel. Is it possible?

I tried to do it with dockers on linux (ubu / The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)), on windows (w10, ws2019), linux with classic installation (fresh official drivers from nvidia, fresh CUDA, 3 versions of Hashcat), but have no result





hashcat (v6.2.6) 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
* Device #3: 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 #4: 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 #5: 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 #6: 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 #7: 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 #8: 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 #9: Outdated POCL OpenCL driver detected!

This OpenCL driver may fail kernel compilation or produce false negatives.
We recommend using a version of POCL >= 1.9
You can use --force to override, but do not report related errors.

CUDA API (CUDA 12.0)
====================
* Device #1: NVIDIA GeForce RTX 4090, 23820/24217 MB, 128MCU
* Device #2: NVIDIA GeForce RTX 4090, 23820/24217 MB, 128MCU
* Device #3: NVIDIA GeForce RTX 4090, 23820/24217 MB, 128MCU
* Device #4: NVIDIA GeForce RTX 4090, 23820/24217 MB, 128MCU
* Device #5: NVIDIA GeForce RTX 4090, 23820/24217 MB, 128MCU
* Device #6: NVIDIA GeForce RTX 4090, 23820/24217 MB, 128MCU
* Device #7: NVIDIA GeForce RTX 4090, 23820/24217 MB, 128MCU
* Device #8: NVIDIA GeForce RTX 4090, 23820/24217 MB, 128MCU

OpenCL API (OpenCL 1.2 pocl 1.4, None+Asserts, LLVM 9.0.1, RELOC, SLEEF, DISTRO, POCL_DEBUG) - Platform #1 [The pocl project]
=============================================================================================================================
* Device #9: pthread-Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz, skipped

OpenCL API (OpenCL 3.0 CUDA 12.0.89) - Platform #2 [NVIDIA Corporation]
=======================================================================
* Device #10: NVIDIA GeForce RTX 4090, skipped
* Device #11: NVIDIA GeForce RTX 4090, skipped
* Device #12: NVIDIA GeForce RTX 4090, skipped
* Device #13: NVIDIA GeForce RTX 4090, skipped
* Device #14: NVIDIA GeForce RTX 4090, skipped
* Device #15: NVIDIA GeForce RTX 4090, skipped
* Device #16: NVIDIA GeForce RTX 4090, skipped
* Device #17: NVIDIA GeForce RTX 4090, skipped

Kernel /home/hashcat/OpenCL/m02100-optimized.cl:
Optimized kernel requested, but not available or not required
Falling back to pure kernel

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256

Hashes: 3 digests; 3 unique digests, 3 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Optimizers applied:
* Zero-Byte
* Slow-Hash-SIMD-LOOP

Watchdog: Temperature abort trigger set to 90c

Host memory required for this attack: 11802 MB

Dictionary cache hit:
* Filename..: /home/hashcat/dict/rockyou.txt
* Passwords.: 28242362
* Bytes.....: 351593161
* Keyspace..: 28242362

Approaching final keyspace - workload adjusted.         

[s]tatus [p]ause [b]ypass [c]heckpoint [f]inish [q]uit =>

Session..........: dcc2
Status...........: Running
Hash.Mode........: 2100 (Domain Cached Credentials 2 (DCC2), MS Cache 2)
Hash.Target......: dcc2.hash
Time.Started.....: Wed Jan 25 19:04:58 2023 (8 secs)
Time.Estimated...: Wed Jan 25 19:05:06 2023 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (/home/hashcat/dict/rockyou.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........:  1739.6 kH/s (65.73ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Speed.#2.........:  1747.2 kH/s (47.42ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Speed.#3.........:  1727.7 kH/s (65.91ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Speed.#4.........:  1772.5 kH/s (76.23ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Speed.#5.........:  1706.6 kH/s (66.70ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Speed.#6.........:  1742.1 kH/s (48.11ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Speed.#7.........:  1767.0 kH/s (66.48ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Speed.#8.........:  1751.5 kH/s (76.48ms) @ Accel:32 Loops:1024 Thr:512 Vec:1
Speed.#*.........: 13954.1 kH/s
Recovered........: 0/3 (0.00%) Digests (total), 0/3 (0.00%) Digests (new), 0/3 (0.00%) Salts
Progress.........: 83748376/84727086 (98.84%)
Rejected.........: 0/83748376 (0.00%)
Restore.Point....: 20412640/28242362 (72.28%)
Restore.Sub.#1...: Salt:2 Amplifier:0-1 Iteration:9216-10239
Restore.Sub.#2...: Salt:2 Amplifier:0-1 Iteration:9216-10239
Restore.Sub.#3...: Salt:2 Amplifier:0-1 Iteration:9216-10239
Restore.Sub.#4...: Salt:2 Amplifier:0-1 Iteration:9216-10239
Restore.Sub.#5...: Salt:2 Amplifier:0-1 Iteration:9216-10239
Restore.Sub.#6...: Salt:2 Amplifier:0-1 Iteration:9216-10239
Restore.Sub.#7...: Salt:2 Amplifier:0-1 Iteration:9216-10239
Restore.Sub.#8...: Salt:2 Amplifier:0-1 Iteration:9216-10239
Candidate.Engine.: Device Generator
Candidates.#1....: tarnowstrasse44 -> Tatianaandreea30*
Candidates.#2....: kurisu141250 -> Voluscore@$12
Candidates.#3....: arcadeblazeserver -> �h���u��=�&�v�
Candidates.#4....: Fika11121989 -> commerce.123
Candidates.#5....: h5gyZqZD+6&,2jr -> #f^Su*=y#xrZD,8
Candidates.#6....: Mid_Powrr99th -> bsmarlink2022
Candidates.#7....: puto70correito -> january12222012
Candidates.#8....: 1234567890dmo -> Gustiayu@12345
Hardware.Mon.#1..: Temp: 53c Fan: 76% Util: 99% Core:2790MHz Mem:10251MHz Bus:1
Hardware.Mon.#2..: Temp: 48c Fan: 78% Util:  0% Core:2535MHz Mem:10251MHz Bus:1
Hardware.Mon.#3..: Temp: 75c Fan: 79% Util: 99% Core:2715MHz Mem:10251MHz Bus:1
Hardware.Mon.#4..: Temp: 51c Fan: 83% Util:  0% Core:2535MHz Mem:10251MHz Bus:1
Hardware.Mon.#5..: Temp: 48c Fan: 73% Util: 15% Core:2775MHz Mem:10251MHz Bus:1
Hardware.Mon.#6..: Temp: 43c Fan: 69% Util:  0% Core:2745MHz Mem:10251MHz Bus:1
Hardware.Mon.#7..: Temp: 51c Fan: 76% Util:  0% Core:2760MHz Mem:10251MHz Bus:1
Hardware.Mon.#8..: Temp: 50c Fan: 80% Util:  0% Core:2730MHz Mem:10251MHz Bus:1

RE: dcc2 not work on optimized kernel - Banaanhangwagen - 01-26-2023

As you can read in the output...

Code:
Kernel /home/hashcat/OpenCL/m02100-optimized.cl:
Optimized kernel requested, but not available or not required
Falling back to pure kernel


RE: dcc2 not work on optimized kernel - MidnightHunter - 01-26-2023

(01-26-2023, 10:54 AM)Banaanhangwagen Wrote: As you can read in the output...

Code:
Kernel /home/hashcat/OpenCL/m02100-optimized.cl:
Optimized kernel requested, but not available or not required
Falling back to pure kernel

emm, yes, thank you)

But what I need to do? update OpenCL? Refresh m02100-optimized.cl separately? 

Is it possible to work on optimized kernel with dcc2?

RE: dcc2 not work on optimized kernel - Snoopy - 01-26-2023

(01-26-2023, 11:23 AM)MidnightHunter Wrote:
(01-26-2023, 10:54 AM)Banaanhangwagen Wrote: As you can read in the output...

Code:
Kernel /home/hashcat/OpenCL/m02100-optimized.cl:
Optimized kernel requested, but not available or not required
Falling back to pure kernel

emm, yes, thank you)

But what I need to do? update OpenCL? Refresh m02100-optimized.cl separately? 

Is it possible to work on optimized kernel with dcc2?

there is no optimized kernel for this specific mode