Open dstaley opened 10 years ago
Good to hear ! The fact that you had to rename the libavl file is really strange ...
I think it's because libavl is a pretty obscure library. The repos didn't have it, so I had to pilfer an RPM from OpenSUSE.
I managed to make it to this:
clean/X930.rule loaded [0]
clean/X940.rule loaded [0]
clean/X990.rule loaded [0]
clean/X950.rule loaded [0]
clean/X960.rule loaded [0]
[3] EXITS
[5] EXITS
[2] EXITS
clean/X970.rule loaded [0]
[4] EXITS
[0] EXITS
clean/X980.rule loaded [0]
[1] EXITS
start crunching
What's the next step?
Hmm, looks like it just failed silently? It might be that I'm using an incompatible version of John, or that the libavl I have isn't functioning properly. Do you happen to remember what your system configuration looked like the last time you were able to run this successfully?
Edit: Okay, looks like it's definitely not compatible with John 1.8.0, which removed the -config
flag. I've compiled 1.7.9-jumbo5 and am giving it a go.
The threshold is probably too high. Reduce the value in the "limit" file and try again.
I spun up an EC2 instance since I don't have access to a machine with 16GB of RAM (and I had difficultly installing libavl on OS X), cloned the repo, installed a libavl RPM (since it's not part of the package manager), and then ran
make
. This was the result:This is the output of
ldd
when run on therf
binary:Alright, I feel really dirty about this, but I simply copied libavl.so.1.5 to libavl.so.1, which fixed that error.
There were several nonexistant files that it complained about, but simply creating the directory and touching the files seemed to fix that.
Currently it's running John with different configurations. Hopefully that means it's working!