hashcat Forum

@dindolo1979

This post is just to let you know that both ethereum algorithms are now available in the newest beta version of hashcat (beta 3.5.0+168 or newer, https://hashcat.net/beta/).

See https://twitter.com/hashcat/status/871117632363261952 , https://github.com/hashcat/hashcat/issues/1227 and https://github.com/hashcat/hashcat/issues/1228 for the details/announcement.

To "extract the hashes" you can run ethereum2john.py (https://raw.githubusercontent.com/magnum...um2john.py) on the Geth/Mist/MyEtherWallet etc json file.

So - Did you recover your Ethereum password? And was it a presale wallet?

"Both algorithms" - is this meaning presale wallets? (sorry, i'm new)

I think they mean PBKDF2 and SCRYPT. There's another one, a third one, which is presale wallets, but they are not yet supported.

Upvoting for support on pre-sale

Another upvote for presale from me, its probably the most wanted of all the versions but yet has been left behind JTR has presale support but there are some features unique to Hashcat i would like to try.

Hello all guys, 
sorry for not responding to the fabolous support you gave to me...and NO I was not able to recover my wallet :-(

Also I'm still struggling for understand how to do that now that ethereum arose much more than the time of first email...it is so sad and make me furious.

Anyway I'm trying always to use @philmd perl script to try to recover my password but if HASHCAT will introduce a module by which I can attack the wallet I would appreciate a lot...A LOT !

@philmd

Quote:you mentioned 3 words, these specific 3 words concatenated together make up a length of 21. I'm not yet sure why you mention that the password is 23 to 25 characters long. Maybe the example words are not the real ones... that's not that important... but it's actually important how many words need to be tried etc... maybe you can explain this a little bit more (e.g. how many base words and how you end up with a lenght of 25, are there any separators between the words etc?)

• 3 words
  
• obviously the words are different
  
• no separator
  
• can be at the end a '#' or a '*'
  
• some vocals are in format like a->@ e->€
  
• every name can have a capital letter
  

So I'm surprised too to have generated a 195GB dictionary also if I know that all the combinations are a huge quantity.


@solace yes it is a presale wallet.

Thank you for all

Hmm, you should be a little bit more specific about which "perl script" your are speaking about.
I probably posted too many perl scripts on the hashcat forum already so it's not easy enough for me to understand about which specific script you are speaking about.

I think the only perl script that should work with pre-sale "hashes" is the one from here:
https://github.com/hashcat/hashcat/issue...-351716733

The other ones were not meant for pre-sale ethereum wallets (and therefore you can't use them to crack pre-sale wallets).

You should really have a look at the github issue... it also mentiones how this format (pre-sale) could be implemented into hashcat etc. Again, the link is this one: https://github.com/hashcat/hashcat/issues/1279

update for ethereum modes supported by hashcat:
we recently also added -m 16300 = Ethereum Pre-Sale Wallet, PBKDF2-HMAC-SHA256 (https://github.com/hashcat/hashcat/pull/1476) which is currently supported by the beta version (https://hashcat.net/beta/). Please test it if you have pre-sale ethereum hashes (you can use ethereum2john.py to convert the json file to a hash, remove the file names before the hash)

Hello all,
VERY LONG POST ! Sorry :-(

if I had recovered my wallet the whole world would know it :-( but I'm not giving up...damn pre-sale :-)
I'm going crazy in analyze the encseed generation for ETHE Pre-Sale wallet.
I tried Hashcat and JTR on p3 instances with 8 Tesla GPU...but I re-discovered that force is weak than wiliness.

I need, if is it possibile, to some one that understand cryptography better than me, so ANY help is really appreciated...also if someone will be critic, but not offensive, I'll appreciate because probably I have a wrong vision in my strategy. I want to being helped in cracking password but I have the need to divide the KEY from the SEED...I explain here so nobody can access to my wallet; something like public/private key method.

THE GOAL IS understand how many bytes are reserved for the KEY=pbkdf2(PW) and how many are for the SEED in the ENCSEED.

I tried everywhere to find a standard, a description, a blog, a note in the internet for understand how the encseed is produced not in terms of algorithms but, instead, in terms of quantity.
So...until now I have gained this informations

***ONE***
https://blog.ethereum.org/2014/07/09/how...r-presale/ I know that ENCSEED=encrypt(KEY, SEED) so in the encseed and, for what I understand, I can find the encrypted password that is given from the function pbkdf2(the-damn-string-I-wrote) then KEY=pbkdf2(PW).

***TWO***
Now from here https://en.wikipedia.org/wiki/PBKDF2 I know that pbkdf2 is a pseudo random function that generates, through a lot of iterations, a very strong key bytes for the password.

The problem is that I'm not able to understand which is the range of the byte lenght requested by Ethereum pre-sale wallet, because having this information I could be able to split my password [KEY=pbkdf2(MyDamnString)] from my SEED through a decryption function.

Having this results could make me in position to be helped in cracking password without giving the SEED that would complete the informations for access to my wallet.

So supposing that my encseed is the following...not actually my encseed

encseed=2df76a064852bd734e47e83b8d245b22b93d06e4b943eccd45718963d809ff742331e3a6620d3934a9ab52a28fab4b83ec010fc055a9f9f2a98af040b017b098d2a7f584ed2cb35cc6a89b72db33af301c9a48c0c3370248ba87dfb05fcf1545fa1f9ff2438bb70d60ab11e90d5bfb4551403e9b9a553741bc36ae957258ce9f3bf1b23f2d4a8cacfc3acb5eea0fc599e5880792b35392df84bd1b54357ae7ad9efcfc6b385f8595ac099d990fd4d3232f5f9bfab5da3d0fc0083a0b8a07c7a501b824a8747802539dc9387b1da4334c76db18eb904c72aa68100e3b21412e08aaacf1ffe54592ad20744f54f4ecb4a5de14cc786c7b44035b500547b9c535d211a8e999e486d81b374761221657bbabbfad5434cab53dccb52bd1750e76277aacecbef84b6e1079de384974a91b7e892a559462cd8d52148ecbbe2b2ba5c38e

This encseed is 640 bytes long.
-How many bytes for the KEY ?
-How many bytes for the SEED ?

Is there any one that can help me...I don't want a solution but if someone knows where to study I would appreciate it a lot ?
ITHANK YOU in advance