Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
PS C:\hashcat-6.2.4\hashcat-6.2.4> ./hashcat.exe -a 0 -m 1000 .\hashes.txt .\rockyou.txt
hashcat (v6.2.4) starting
CUDA API (CUDA 11.5)
====================
* Device #1: NVIDIA GeForce GTX 1070, 7243/8191 MB, 15MCU
OpenCL API (OpenCL 3.0 CUDA 11.5.76) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce GTX 1070, skipped
OpenCL API (OpenCL 3.0 WINDOWS) - Platform #2 [Intel(R) Corporation]
====================================================================
* Device #3: Intel(R) Core(TM) i7-8700 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
Rules: 1
Optimizers applied:
* Zero-Byte
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Raw-Hash
ATTENTION! Pure (unoptimized) backend kernels selected.
Pure kernels can crack longer passwords, but drastically reduce performance.
If you want to switch to optimized kernels, append -O to your commandline.
See the above message to find out about the exact limits.
Watchdog: Temperature abort trigger set to 90c
Host memory required for this attack: 263 MB
Dictionary cache hit:
* Filename..: .\rockyou.txt
* Passwords.: 14344396
* Bytes.....: 139921601
* Keyspace..: 14344396
Approaching final keyspace - workload adjusted.
Cracking performance lower than expected?
* Append -O to the commandline.
This lowers the maximum supported password/salt length (usually down to 32).
* Append -w 3 to the commandline.
This can cause your screen to lag.
* Append -S to the commandline.
This has a drastic speed impact but can be better for specific attacks.
Typical scenarios are a small wordlist but a large ruleset.
* Update your backend API runtime / driver the right way:
https://hashcat.net/faq/wrongdriver
* Create more work items to make use of your parallelization power:
https://hashcat.net/faq/morework
Session..........: hashcat
Status...........: Exhausted
Hash.Mode........: 1000 (NTLM)
Hash.Target......: REDACTED
Time.Started.....: Wed Nov 17 21:13:09 2021 (24 secs)
Time.Estimated...: Wed Nov 17 21:13:33 2021 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (.\rockyou.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........: 607.8 kH/s (0.05ms) @ Accel:2048 Loops:1 Thr:32 Vec:1
Recovered........: 0/1 (0.00%) Digests
Progress.........: 14344396/14344396 (100.00%)
Rejected.........: 0/14344396 (0.00%)
Restore.Point....: 14344396/14344396 (100.00%)
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:0-1
Candidate.Engine.: Device Generator
Candidates.#1....: $HEX[20313130373836] -> $HEX[042a0337c2a156616d6f732103]
Hardware.Mon.#1..: Temp: 37c Fan: 31% Util: 6% Core: 258MHz Mem: 405MHz Bus:16
Started: Wed Nov 17 21:13:08 2021
Stopped: Wed Nov 17 21:13:34 2021
PS C:\hashcat-6.2.4\hashcat-6.2.4>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment