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 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.
