Line-length exception....

[onis_uk]

Right got it working ...... notice the first part of my has was

$ethereum$s*262144*8*1*

but the example has was

$ethereum$s*262144*1*8*

so I swapped the 1 and 8 around ....... also etc part of the hash needs to be 64 long my middle section was 62 so i prefaced it with 00

[onis_uk]

OK, so now I can get it to run (sort of) it just hangs at this screen and crases my amd driver.
I'm guessing that's because my max password length seems to be set at 256! 
How do I change that? with a mask?

[cqdx]

OK, so now I can get it to run (sort of) it just hangs at this screen and crases my amd driver.
I'm guessing that's because my max password length seems to be set at 256! 
How do I change that? with a mask?

Add -D 1 (not -d 1) to command line to use CPU
More info here https://stealthsploit.com/2018/01/04/eth...pu-vs-cpu/
Why CPU ? Read in the article
Yet I hope that I am wrong and there is a way to run cracking on GPU

[cqdx]

Right got it working ...... notice the first part of my has was

$ethereum$s*262144*8*1*

but the example has was

$ethereum$s*262144*1*8*

so I swapped the 1 and 8 around ....... also etc part of the hash needs to be 64 long my middle section was 62 so i prefaced it with 00

about 62 char salt (or ciphertext ?) i wrote here https://hashcat.net/forum/thread-7202-po...l#pid38734
sometime salt has 63 or 62 char salt. I think Hashcat chk if salt not 64 char - and show error (

[onis_uk]

Ah yes I remember reading about this kind of has being "gpu proof" lol 

my cpu says this.......

[onis_uk]

used the --force to make it work............

finally hashing...... at 5H/s lol ..........

[cqdx]

Ah yes I remember reading about this kind of has being "gpu proof" lol 

my cpu says this.......

-D 1 is not same -d 1 (and not even the same -D 2)
just use -D 1

  hashcat_1.png (Size: 6.24 KB / Downloads: 2)

  hashcat_2.png (Size: 2.62 KB / Downloads: 1)

[cqdx]

used the --force to make it work............

finally hashing...... at 5H/s lol ..........

lol, yes
same sh#t bro

[onis_uk]

used the --force to make it work............

finally hashing...... at 5H/s lol ..........

lol, yes
same sh#t bro

Time.Estimated...: Next Big Bang (> 10 years) at least its honest lol and that was using a mask of what I think it is....

so no current work around for v3 hashes??

[undeath]

$ethereum$s*262144*8*1*

but the example has was

$ethereum$s*262144*1*8*

so I swapped the 1 and 8 around

that will make your hash uncrackable. those are the scrypt settings and they are present in the "hash" string for a reason.