hashcat Forum › Support › hashcat v
So I'm dumb and lost my ETH password

Thread Closed 
Threaded Mode
So I'm dumb and lost my ETH password
DumberThanDumb Offline
Junior Member
**
Posts: 11
Threads: 1
Joined: Aug 2017
#21
08-09-2017, 09:56 PM (This post was last modified: 08-10-2017, 04:34 AM by DumberThanDumb.)
It took more time before failing(about 30 seconds), but didn't work.

Code:
C:\Users\Miner 1\Desktop\hashcat-3.6.0>hashcat64.exe -a 3 -m 15700 -w 2 --scrypt-tmto=0 -n 1 -D 2 --force hash.hash BLABLA6?a?a?a -o cracked.txt
hashcat (v3.6.0) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) Celeron(R) CPU G3930 @ 2.90GHz, skipped.

OpenCL Platform #2: NVIDIA Corporation
======================================
* Device #2: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU
* Device #3: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU
* Device #4: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU
* Device #5: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU
* Device #6: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU
* Device #7: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU

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

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force

Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

Increasing single-block device memory allocatable for --scrypt-tmto 0.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
Increasing single-block device memory allocatable for --scrypt-tmto 0.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
Increasing single-block device memory allocatable for --scrypt-tmto 0.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
Increasing single-block device memory allocatable for --scrypt-tmto 0.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
Increasing single-block device memory allocatable for --scrypt-tmto 0.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
Increasing single-block device memory allocatable for --scrypt-tmto 0.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE



clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE





clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE





clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE



clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE





clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE

[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit => clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILUREclEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE



clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE


clEnqueueNDRangeKernel(): CL_MEM_OBJECT_ALLOCATION_FAILURE




Session..........: hashcat
Status...........: Exhausted
Hash.Type........: Ethereum Wallet, SCRYPT
Hash.Target......: $ethereum$s*262144*8*1*d6....1a28450365a5578798a...ad5b30
Time.Started.....: Wed Aug 09 12:53:54 2017 (0 secs)
Time.Estimated...: Wed Aug 09 12:53:54 2017 (0 secs)
Guess.Mask.......: BLABLA6?a?a?a [10]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....:        0 H/s (0.00ms)
Speed.Dev.#3.....:        0 H/s (0.00ms)
Speed.Dev.#4.....:        0 H/s (0.00ms)
Speed.Dev.#5.....:        0 H/s (0.00ms)
Speed.Dev.#6.....:        0 H/s (0.00ms)
Speed.Dev.#7.....:        0 H/s (0.00ms)
Speed.Dev.#*.....:        0 H/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0/857375 (0.00%)
Rejected.........: 0/0 (0.00%)
Restore.Point....: 0/857375 (0.00%)
Candidates.#2....: BLABLA6988 -> BLABLA6145
Candidates.#3....: BLABLA6823 -> BLABLA63!!
Candidates.#4....: BLABLA6ach -> BLABLA6mch
Candidates.#5....: BLABLA6b45 -> BLABLA6r56
Candidates.#6....: BLABLA6*++ -> BLABLA6pwa
Candidates.#7....: BLABLA6e98 -> BLABLA6yke
HWMon.Dev.#2.....: Temp: 52c Fan:  0% Util: 78% Core:1594MHz Mem:4333MHz Bus:1
HWMon.Dev.#3.....: Temp: 55c Fan:  0% Util: 83% Core:1569MHz Mem:4463MHz Bus:1
HWMon.Dev.#4.....: Temp: 48c Fan:  1% Util: 38% Core:1556MHz Mem:4579MHz Bus:1
HWMon.Dev.#5.....: Temp: 49c Fan:  0% Util: 68% Core:1582MHz Mem:4551MHz Bus:1
HWMon.Dev.#6.....: Temp: 42c Fan: 31% Util: 84% Core:1531MHz Mem:4635MHz Bus:1
HWMon.Dev.#7.....: Temp: 53c Fan:  0% Util: 14% Core:1582MHz Mem:4449MHz Bus:1

Started: Wed Aug 09 12:53:17 2017
Stopped: Wed Aug 09 12:53:56 2017

C:\Users\Miner 1\Desktop\hashcat-3.6.0>pause
Press any key to continue . . .




The other 2 pc doesn't like it better, yet all driver are up to date (only copied one of the 2, since they produce similar return):

Code:
* Device #1: Intel's OpenCL runtime (GPU only) is currently broken.
            We are waiting for updated OpenCL drivers from Intel.
            You can use --force to override, but do not report related errors.
* 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
OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) HD Graphics 4600, skipped.
* Device #2: Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz, skipped.

OpenCL Platform #2: NVIDIA Corporation
======================================
* Device #3: GeForce GTX 970, 1024/4096 MB allocatable, 13MCU

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

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force

Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

Increasing single-block device memory allocatable for --scrypt-tmto 0.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
Increasing single-block device memory allocatable for --scrypt-tmto 4.
clGetEventProfilingInfo(): CL_OUT_OF_RESOURCES

nvmlDeviceGetTemperature(): Unknown Error

clFlush(): CL_OUT_OF_RESOURCESnvmlDeviceGetFanSpeed(): Unknown Error



clFlush(): CL_OUT_OF_RESOURCES

clFlush(): CL_OUT_OF_RESOURCES

nvmlDeviceGetUtilizationRates(): Unknown Error

[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit => clFlush(): CL_OUT_OF_RESOURCES

nvmlDeviceGetClockInfo(): Unknown Error

nvmlDeviceGetClockInfo(): Unknown Error

nvmlDeviceGetCurrPcieLinkWidth(): Unknown Error

Session..........: hashcat
Status...........: Exhausted
Hash.Type........: Ethereum Wallet, SCRYPT
Find
undeath Offline
Sneaky Bastard
******
Posts: 2,301
Threads: 11
Joined: Jul 2010
#22
08-10-2017, 04:55 PM (This post was last modified: 08-10-2017, 05:25 PM by undeath.)
I just learnt script-tmto=0 means auto-configuration, not disable tmto trade-offs alltogether. And furthermore, the higher the value the less RAM is used.

However, there might be an incompatibility with the ethereum2john.py script and hashcat's hash parser. I'm waiting for someone who knows the technicalities to check on that. Hopefully someone will post an update here soon. edit: it probably works as expected according to my tests
Find
slayerdiangelo Offline
Member
***
Posts: 73
Threads: 14
Joined: Jun 2017
#23
08-10-2017, 05:32 PM
Wow!I can see that the situation has got intense for a noob\dumb user!
Find
undeath Offline
Sneaky Bastard
******
Posts: 2,301
Threads: 11
Joined: Jul 2010
#24
08-10-2017, 05:35 PM
take home message: the scrypt settings ethereum uses by default make GPU cracking mostly impossible. Just use your CPU.
Find
DumberThanDumb Offline
Junior Member
**
Posts: 11
Threads: 1
Joined: Aug 2017
#25
08-10-2017, 06:14 PM
I read that gpu related notice before, but I also saw people get about 30h/s with the 1080 on eth scrypt, so I thought it would simply not be able to give the awesome gpu performance yet still faster than the cpu for each 1070. Since I have a 6x gtx1070 I wanted to try it but guess I will simply stick to cpu.

Thanks for all the help!
Find
undeath Offline
Sneaky Bastard
******
Posts: 2,301
Threads: 11
Joined: Jul 2010
#26
08-11-2017, 10:12 AM
scrypt has three parameters. Depending on how those parameters are chosen it may or may not work on GPU. The parameters of your ethereum wallet don't.
Find
Thread Closed