Topic: Using John the Ripper to crack wallet (Read 4799 times)

Your right the bleeding-jumbo is the most recent and already has the external mode i needed defined, now lets use it

I don't really know, I haven't used john.  I just noticed the code you originally linked might be outdated since they'd made newer versions.  So you should probably update to bleeding-jumbo and build that.  I just noticed your comment on PR #241 and the response.  The .h file problem is because they are supposed to be generated by the build process.  Are you following the build instructions in doc/INSTALL?  Sometimes when you check code out of git or svn, there is an initial step you have to do to generate some files that aren't kept in the repository, but I'm not seeing any notes about that so maybe it doesn't apply here.

It looks like the python script is a pre-cracking step that extracts out the master key into a standard john input format, and then compiled C code cracks it like normal (I don't know what "normal" is because I haven't used it.)  The cracking code is here.  There's an author email address at the top, and it was only written last month, so the author might be able to help if you have trouble.

If you're new to using this program, I would suggest finding a tutorial that walks you through cracking something easy, get that working with a bleeding-jumbo build, then try plugging in the output of the python script in place of the hash or whatever the tutorial's input was.  Maybe even "crack" a test wallet you know the password to, to make sure it's all working before you start with the real wallet.

Scintill are you saying I should use that python script or update to bleeding-jumbo patch? I fixed the openssl issue only now the .h files he used aren't in any of the directories I looked through. I am using jumbo 1.7.9 currently. And when your as poor as I am you wont stop easily at this. stupid mistake but at least I am learning tons of CS over it 

I tried to do the same using jack the ripper but to no avail, had around 20~ BTC in the wallet, of course back then it was only worth around $200, it would be great to still have it now

you're going to all this length to crack a wallet that has like BTC1.2 in??

you might as well just write that money off. The cost of the time and energy required to crack the wallet will far exceed the amount of money you'll get from the wallet.

And millions and millions of years when it comes to wallets

you just need a good mining rig to break a password

Isn't that what you would want to say to get some help with the issue? It can't take that long to try the 50-60 passwords you use normally.

That's what GravePhoenix, first time poster, says he's trying. Better not place your trust so easily on bitcoin world. :-)

Did you even read his post?
He's trying to recover his wallet's password.

Stealing people's wallets is bad... m'kay.

The end of that pull request says they fixed some problems and made a new PR.  It seems to be #242.  Then they closed that and said they merged to "bleeding-jumbo" branch.  I'm seeing it here: https://github.com/magnumripper/JohnTheRipper/blob/bleeding-jumbo/run/bitcoin2john.py.

So I've been locked out of my wallet because I forgot the passphrase to a secondary walllet and now I have about 140$ in there and am trying to get it out using John the ripper and this code(https://github.com/magnumripper/JohnTheRipper/pull/241) as an external mode to crack it. When I run it though I always get an error stating that the line :include which is the first line in the code is an invalid identifier. Help greatly appreciated and I might send some coins your way if you prove very useful