Ethereum wallet length exception

[r0tty]

Hi folks,

I am trying open my Ethereum wallet from my saved wallet.json file.  I have converted the file using this as suggested in another post I found searching for this issue;

https://github.com/magnumripper/JohnTheR...um2john.py

I am attempting this with minimal options from the command line so as to not confuse the process and keep it a simple as possible to troubleshoot.  Here is the command issued:

hashcat64.exe -m 15700 hash.txt -D1 -a 3 hash?l?l?l

The error I get follows:

Hashfile 'hash.txt' on line 1 (hash.txt:<INSERT HASH HERE>): Line 
-length exception
No hashes loaded.

Can anyone point me in the right direction to get past this?
Thanks in advance....

BTW: If someone can help me get this open I will gladly tip them

[atom]

Did you remove the "username" part? That is the stuff before and including the : char.

See https://hashcat.net/wiki/doku.php?id=example_hashes for an example hash

[Villan]

I'm having the same error. In my case two things I want to mention.

1. I have a presale wallet (PBKDF2-HMAC-SHA256) that produces a hash with $ethereum$w* rather than $ethereum$p*

2. I don't know whether its of any relevance with Hashcat but over at JTR they had issues with hashes being too long as ref here https://github.com/magnumripper/JohnTheR...-307943997 . My output of ethereum2john.py is a 1334 character line. Are there any hash length limits with hashcat as well?

[Chick3nman]

Ethereum Presale ($ethereum$w*) are not supported by hashcat yet. You can track the addition status via the github issue here: https://github.com/hashcat/hashcat/issues/1279

[r0tty]

It was the filename string inside the file that was preventing it from running, thanks!

Now, another error:

Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger disabled.

clCreateBuffer(): CL_MEM_OBJECT_ALLOCATION_FAILURE

What might cause this?

[r0tty]

D:\hashcat-3.6.0>hashcat64.exe -m 15700 hash.txt -d 1 -a 3 hash?l?l?l
hashcat (v3.6.0) starting...

ADL_Overdrive6_TargetTemperatureData_Get(): -8

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: Hawaii, 4048/8192 MB allocatable, 44MCU
* Device #2: AMD FX(tm)-9590 Eight-Core Processor, skipped.

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.
Increasing total device memory allocatable for --scrypt-tmto 5.
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_FAILURE

[MrMeeseeks]

D:\hashcat-3.6.0>hashcat64.exe -m 15700 hash.txt -d 1 -a 3 hash?l?l?l
hashcat (v3.6.0) starting...

ADL_Overdrive6_TargetTemperatureData_Get(): -8

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: Hawaii, 4048/8192 MB allocatable, 44MCU
* Device #2: AMD FX(tm)-9590 Eight-Core Processor, skipped.

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.
Increasing total device memory allocatable for --scrypt-tmto 5.
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_FAILURE

Atom has answered this question in this thread which was found using the search function: https://hashcat.net/forum/thread-6652-po...l#pid35493