+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Misc (https://hashcat.net/forum/forum-15.html)
+--- Forum: General Talk (https://hashcat.net/forum/forum-33.html)
+--- Thread: Geth Ethereum Keystore password recovery (/thread-12439.html)
Pages:
1
2
RE: Geth Ethereum Keystore password recovery - LowellChief - 01-03-2025
(01-02-2025, 04:10 PM)svobodnui11 Wrote:(01-02-2025, 08:19 AM)LowellChief Wrote: Thanks again for the help. I entered my version of the command in your example but kept getting an error when I combined the attack mode 1 with the best64 rule.
I figured out a way to combine the 2 txt files a different way. Is there a place to download some of the other rules other than what come with the HC download? Specifically, the One rule to rule them all and possibly the unix ninja rule.
Thanks again for the help.
ask on Google this - OneRuleToRuleThemAll.rule
but maybe best choice is - hashcat-utils-1.9\bin\combinator.exe for you
Thank you and the Combinator exe. was how I merged my two lists and then I copied the list after the stdout command.
I have done that on Google and I was also looking at the updated One Rule which I found on Github but when I tried to download on my Chromebook(probably the problem) the page crashed.
https://github.com/stealthsploit/OneRuleToRuleThemStill
RE: Geth Ethereum Keystore password recovery - LowellChief - 01-05-2025
Just wanted to see if there's anything I can do to optimize my system for HC. Here's my benchmark test results. Thank you for helping this noob in advance.
.\hashcat.exe --benchmark -m 15700
hashcat (v6.2.6) 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 12.7)
====================
* Device #1: NVIDIA GeForce RTX 4070 SUPER, 11053/12281 MB, 56MCU
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, skipped
Benchmark relevant options:
===========================
* --optimized-kernel-enable
----------------------------------------------------------------
* Hash-Mode 15700 (Ethereum Wallet, SCRYPT) [Iterations: 262144]
----------------------------------------------------------------
Speed.#1.........: 1 H/s (7.71ms) @ Accel:1 Loops:1024 Thr:4 Vec:1
Started: Sun Jan 05 14:25:22 2025
Stopped: Sun Jan 05 14:25:34 2025
RE: Geth Ethereum Keystore password recovery - slyexe - 01-05-2025
use your CPU, use -d 3. Otherwise, no the hashrate will be seriously slow.
RE: Geth Ethereum Keystore password recovery - LowellChief - 01-06-2025
(01-05-2025, 11:28 PM)slyexe Wrote: use your CPU, use -d 3. Otherwise, no the hashrate will be seriously slow.
Thank you. When I use -d 3 , I get "No Devices Found/Left" from Hashcat
Any ideas?
RE: Geth Ethereum Keystore password recovery - LowellChief - 01-11-2025
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