Geth Ethereum Keystore password recovery
#15
It's been really fun messing around with Hashcat and learning.  I feel like I'm getting better using it but have much to learn.  I read somewhere on here that  -D and -d have different meanings in the command line.  I looked into this due to HC running only on my GPU and skipping my CPU(Device # 3).  So, I replaced  my -d 1,3 with -D 1,3 and now it only runs from my CPU(Device # 3) and my GPU(device #1 is Skipped).  It is much faster on my CPU however and you can compare my benchmark from an earlier post in this thread to the info below.(27 H/s with using only my CPU vs 1H/s using only my GPU)

My question is if is possible that I can use both devices at the same time so neither one is "Skipped".  I'm not sure if that would increase my hashs per second but if it will make HC run even faster, that would be great.  Oh, I'm using Windows 11 if that make a difference. Thanks for your help!

.\
.\hashcat.exe -a 0 -m 15700 -D 1,3 unrec.txt prime.txt -w 3 -r rules/toggles2.rule
hashcat (v6.2.6) starting


CUDA API (CUDA 12.7)
====================
* Device #1: NVIDIA GeForce RTX 4070 SUPER, skipped

OpenCL API (OpenCL 3.0 CUDA 12.7.33) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 4070 SUPER, skipped

OpenCL API (OpenCL 3.0 WINDOWS) - Platform #2 [Intel(R) Corporation]
====================================================================
* Device #3: AMD Ryzen 7 5700X3D 8-Core Processor, 16315/32694 MB (8173 MB allocatable), 16MCU

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: 120

Optimizers applied:
* Zero-Byte
* Single-Hash
* Single-Salt

Watchdog: Temperature abort trigger set to 90c

Host memory required for this attack: 0 MB

Dictionary cache built:
* Filename..: prime.txt
* Passwords.: 1831
* Bytes.....: 33646
* Keyspace..: 219720
* Runtime...: 0 secs

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

Session..........: hashcat
Status...........: Running
Hash.Mode........: 15700 (Ethereum Wallet, SCRYPT)
Hash.Target......: $ethereum$s*262144*8*1*d8b6
Time.Started.....: Sat Jan 11 10:03:53 2025 (3 secs)
Time.Estimated...: Sat Jan 11 12:20:19 2025 (2 hours, 16 mins)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (prime.txt)
Guess.Mod........: Rules (rules/toggles2.rule)
Guess.Queue......: 1/1 (100.00%)
Speed.#3.........:       27 H/s (1.10ms) @ Accel:16 Loops:1024 Thr:1 Vec:1
Recovered........: 0/1 (0.00%) Digests (total), 0/1 (0.00%) Digests (new)
Progress.........: 80/219720 (0.04%)
Rejected.........: 0/80 (0.00%)
Restore.Point....: 0/1831 (0.00%)
Restore.Sub.#3...: Salt:0 Amplifier:5-6 Iteration:2048-3072
Candidate.Engine.: Device Generator
Candidates.#3....: 
Hardware.Mon.#3..: N/A
Reply


Messages In This Thread
RE: Geth Ethereum Keystore password recovery - by LowellChief - 4 hours ago