Henning Noren

The error indicate that pdfcrack could not find the standard security handler, which is most likely because the document does not use one or there is some newer PDF version that changes things. From the output you pasted, I cannot see the encrypt object that pdfcrack is looking for so it explains the problem (it is unable to find the information needed to start cracking). The first question is of course what kind of encryption that is used, if any, in this document? Is it password protected and if...

Not sure what is going wrong, but this should work: pdfcrack -o -f ./file.pdf -l=./savedstate.sav although both the "-o" and "-f ./file.pdf" are unnecessary, and the following is all that is needed: pdfcrack -l ./savedstate.sav Since all the information for cracking is in the savedstate. I have not heard of a problem with macOS, but to be honest I rarely run it anymore and have no mac to test on. The only thing I can think of is that you did a second run (maybe "pdfcrack -o -f ./file.pdf -l=./savedstate.sav"),...

Actually, had to just do some checks and there is a issue in pdfcrack for loading charsets starting with space. Turns out silly old fscanf was too hard to use for me so I need to look into that, but in the meantime, just move the space from first to second character of the string and you should be fine. I just tested that here. I will see if I can find a fix for it, but it is old code and I need to remember how to make a new release so no promises.

I totally missed the bug... yeah.. I need to look into that with the savedstate.txt loading and what is going on. Will get back to you regarding that this weekend when I find some time to remove the dust around the code

Thanks for the request! I posted a response in the bugticket how to handle those, but I would not be reluctant to patches for the same if anyone would bother coding them up. In case sourceforge ever manages to mess up the links to bugs, here is the trick: * Put the charset you want in a file (usual UTF8 encoding, should probably be standard nowadays) * Use iconv to convert the file to your chosen encoding (here ISO-LATIN-1): iconv -f UTF-8 -t ISO-8859-1 latin1.txt > latin1-actually.txt * Read in...

Oh boy, this little project keeps giving still! Thanks for the report! First of all, you need to be careful that the characters used are actually latin-1 encoded, not just part of the set. In this case the file you provided seems to be UTF-8 so I started by making it latin-1: $ iconv -f UTF-8 -t ISO-8859-1 latin1.txt > latin1-actually.txt $ file latin1-actually.txt latin1-actually.txt: ISO-8859 text $ wc -c latin1-actually.txt 191 latin1-actually.txt $ wc -c latin1-actually.txt latin1.txt 191 latin1-actually.txt...

This is now resolved in pdfcrack-0.20 where the correct error message should be printed.

pdfcrack 0.20