03-02-2022, 08:04 AM
@v71221 I have re-run the same command with v6.2.5. The results are the same.
Again, while I understand that any of those collisions are functionally valid, the ability to obtain the 'correct' collision (hashcat1) is still important.
Code:
PS D:\hashcat-6.2.5> .\hashcat.exe -a 3 -m 14000 a28bc61d44bb815c:1172075784504605 ?1?1?1?1?1?1?1?1 -1 ?l?d --keep-guessing
hashcat (v6.2.5) starting
CUDA API (CUDA 11.2)
====================
* Device #1: GeForce RTX 3090, 23336/24576 MB, 82MCU
* Device #2: GeForce RTX 3090, 23336/24576 MB, 82MCU
OpenCL API (OpenCL 1.2 CUDA 11.2.109) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #3: GeForce RTX 3090, skipped
* Device #4: GeForce RTX 3090, skipped
Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 8
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
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
ATTENTION! --keep-guessing mode is enabled.
This tells hashcat to continue attacking all target hashes until exhaustion.
hashcat will NOT check for or remove targets present in the potfile, and
will add ALL plains/collisions found, even duplicates, to the potfile.
Watchdog: Temperature abort trigger set to 90c
Host memory required for this attack: 2925 MB
a28bc61d44bb815c:1172075784504605:harhbat1
a28bc61d44bb815c:1172075784504605:hasibat1
a28bc61d44bb815c:1172075784504605:harhbau1
a28bc61d44bb815c:1172075784504605:hashcau1
Cracking performance lower than expected?
* 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
a28bc61d44bb815c:1172075784504605:haricat0
a28bc61d44bb815c:1172075784504605:hashbat0
a28bc61d44bb815c:1172075784504605:haricau0
a28bc61d44bb815c:1172075784504605:hashbau0
Approaching final keyspace - workload adjusted.
Session..........: hashcat
Status...........: Exhausted
Hash.Mode........: 14000 (DES (PT = $salt, key = $pass))
Hash.Target......: a28bc61d44bb815c:1172075784504605
Time.Started.....: Wed Mar 02 17:00:17 2022 (25 secs)
Time.Estimated...: Wed Mar 02 17:00:42 2022 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Mask.......: ?1?1?1?1?1?1?1?1 [8]
Guess.Charset....: -1 ?l?d, -2 Undefined, -3 Undefined, -4 Undefined
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........: 54870.9 MH/s (0.36ms) @ Accel:256 Loops:1024 Thr:32 Vec:1
Speed.#2.........: 56273.2 MH/s (0.35ms) @ Accel:256 Loops:1024 Thr:32 Vec:1
Speed.#*.........: 111.1 GH/s
Recovered........: 0/1 (0.00%) Digests
Progress.........: 2821109907456/2821109907456 (100.00%)
Rejected.........: 0/2821109907456 (0.00%)
Restore.Point....: 60455536/60466176 (99.98%)
Restore.Sub.#1...: Salt:0 Amplifier:46080-46656 Iteration:0-1024
Restore.Sub.#2...: Salt:0 Amplifier:46080-46656 Iteration:0-1024
Candidate.Engine.: Device Generator
Candidates.#1....: sdqwr0q6 -> x8qmf8q6
Candidates.#2....: sdqyyyq6 -> x8qqxqgx
Hardware.Mon.#1..: Temp: 52c Fan: 0% Util: 64% Core:1830MHz Mem:10802MHz Bus:16
Hardware.Mon.#2..: Temp: 50c Fan: 0% Util: 60% Core:1860MHz Mem:10802MHz Bus:16
Started: Wed Mar 02 17:00:10 2022
Stopped: Wed Mar 02 17:00:44 2022Again, while I understand that any of those collisions are functionally valid, the ability to obtain the 'correct' collision (hashcat1) is still important.