ePub & PDF decryption on Mac OSX

[epstewart]

Originally Posted by pthwaite

Eric,
No, I'm talking about unzipping your downloaded app.
Generally I use Zipeg for unzipping, but occasionally it runs into problems. (it appears to work but the unzipped app doesn't work. If I unzip using stuffit (the same download) it works and of course vice-versa. (The inbuilt Archive utility doesn't always work for some files which is why I have stuffit and zipeg too)
Once the app is correctly unzipped, it works fine, just like the command line tools. This problem isn't unique to your zipped file, it occurs with a number. I've just learned over the years that archiving/de-archiving packages are not all equal.

Howard,

That impresses me as quite strange behavior! I do occasionally find that some archive files, when they are double clicked, want to open in Stuffit Expander rather than Archive Utility. But even if they pick Stuffit Expander, they basically expand properly every time. Exception: as mentioned in earlier posts to this thread, certain ADE e-books that have known issues with their zip file internal formatting. Other than those, I have never had a problem with expanding zipped files, as long as they have downloaded aright, so I'm scratching my head as to what might be causing your problem.

Later!

Eric

[llreader]

I am having trouble compiling pycrypto. I have the GCC-4.2 installed, but it gives me this error when I try sudo python setup.py build (or with python2.6):

sudo python setup.py build
running build
running build_py
running build_ext
building 'Crypto.Hash.MD2' extension
Compiling with an SDK that doesn't seem to exist: /Developer/SDKs/MacOSX10.4u.sdk
Please check your Xcode installation
gcc-4.0 -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -g -bundle -undefined dynamic_lookup build/temp.macosx-10.3-fat-2.6/src/MD2.o -o build/lib.macosx-10.3-fat-2.6/Crypto/Hash/MD2.so
ld: library not found for -lbundle1.o
collect2: ld returned 1 exit status
ld: library not found for -lbundle1.o
collect2: ld returned 1 exit status
lipo: can't open input file: /var/tmp//ccBhIbdi.out (No such file or directory)
error: command 'gcc-4.0' failed with exit status 1

There is no /Developer/SDKs/MacOSX10.4u.sdk

I have /Developer/SDKs/MacOSX10.5.sdk and /Developer/SDKs/MacOSX10.6.sdk

I think I must have something hanging around from an earlier installation of the SDK that is telling python to use the GCC-4.0

I do have macports AND fink installed, maybe that is causing problems (I had some trouble compiling some ports when I upgraded to Snow Leopard).

Any ideas? Thanks!

[llreader]

OK, I seem to at least have figured out what is wrong. I installed version 2.6 from python.org while I was messing around trying to get everything to work, and that seems to have screwed up the configuration, calling 2.6 some of the time. It switched the "default" to python 2.6, which does not exist. I moved the whole framework to the trash temporarily and typing "python" produces an error, but "/usr/bin/python" works fine. pycrypto builds, and ineptepub.py runs fine.

"env python" runs 2.6. I need to figure out how to set it back in all the places it was changed.

I need to figure out where to set the default back

[epstewart]

Originally Posted by llreader

OK, I seem to at least have figured out what is wrong. I installed version 2.6 from python.org while I was messing around trying to get everything to work, and that seems to have screwed up the configuration, calling 2.6 some of the time. It switched the "default" to python 2.6, which does not exist. I moved the whole framework to the trash temporarily and typing "python" produces an error, but "/usr/bin/python" works fine. pycrypto builds, and ineptepub.py runs fine.

"env python" runs 2.6. I need to figure out how to set it back in all the places it was changed.

I need to figure out where to set the default back

llreader,

Take this with a grain of salt, but ... I had similar problems and found deleting (or, if you want to be able to undo it, moving the folder to the Desktop) the /Library/Frameworks/Python.framework/Versions/2.6/ folder and then reinstalling Python 2.6 and then PyCrypto from their respectively downloaded installers cleared things up.

See

https://www.mobileread.com/forums/sho...7&postcount=53

and its immediately preceding posts.

I'm using Leopard, not Snow Leopard, but maybe the magic is the same. I imagine "going back to square one" with respect to the Python 2.6 and PyCrypto installs makes sure all the needed files and libraries are present and accounted for.

Cheers,
Eric

[llreader]

Thanks Eric,

I have had trouble with python installations like this before, going back years, when the fink version screws something up. I would just like to get back to the standard, built-in version. /usr/bin/python seems to be version 2.6.1 anyway, so it seems ok for now.

[dynabook]

I have installed the Developer Tools and the package

http://tmrc.mit.edu/mirror/twisted/D....5_osx10.5.pkg PyCrypto 2.0.1 for OS X 10.5

I get the error:

This script requires PyCrypto, which must beinstalled separately. Read top-of-script comment for details.

Any help? New to Mac, old hand at PC.
--MH

[llreader]

Originally Posted by dynabook

I get the error:

This script requires PyCrypto, which must beinstalled separately. Read top-of-script comment for details.

Any help? New to Mac, old hand at PC.
--MH

You could try what I did - call python using the full path /usr/bin/python, both to install the package and to run the scripts. You can have some confusion if you have multiple python instances installed (like Zope, or Plone, or something else). A lot of packages install python these days - I just found a copy in my OSGeo4W installation on BootCamp.

[dynabook]

I tried /usr/bin/python2.5 which worked so the PyCrpyto is installed with Python 2.5 and not 2.6. Is there a way to install it under 2.6?

[llreader]

Originally Posted by dynabook

I tried /usr/bin/python2.5 which worked so the PyCrpyto is installed with Python 2.5 and not 2.6. Is there a way to install it under 2.6?

Sure, in the pycrypto top directory, where "setup.py" is, try "sudo /usr/bin/python2.6 setup.py install" - On my Mac /usr/bin/python2.6 is a simlink to /System/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 (which I deleted).

You can see what is in there with "ls -l /usr/bin/python*"

You can also try "build" before "install", just to test it, but then you have to type "install" afterward to actually install it.

What happened to me is that the 2.6 version of python, for some reason, made pycrypto try to compile with gcc-4.0 (which I don't have - I have gcc-4.2). I still haven't figured out why it did that, but I think it has something to do with the python installer.

If you are on Snow Leopard, I think the installed python is 2.6.1 (at least that is what I get if I run /usr/bin/python).

Good luck!

[evdberg]

@epstewart,
When running ADEPTKey Generator 1.1a I get the following error:

unable to load Private Key
4386:error:0906D064:PEM routines:PEM_read_bio:bad base64 decode:pem_lib.c:757:

Any idea what is wrong? I am running OS-X 10.5

[epstewart]

Originally Posted by evdberg

@epstewart,
When running ADEPTKey Generator 1.1a I get the following error:

unable to load Private Key
4386:error:0906D064:PEM routines:PEM_read_bio:bad base64 decode:pem_lib.c:757:

Any idea what is wrong? I am running OS-X 10.5

evdberg,

No idea. Could you tell me exactly in what form that message appears, i.e., is it in a dialog box, in Terminal, or what? Also, does it appear before or after you have been asked where to put the output ADEPT key file?

Or, try running the script from Script Editor. Download and unzip

link removed

then open the .scpt file in Script Editor and click on the Run button.

I can tell you that "unable to load Private Key" is not a message the script itself generates. But the script invokes a Unix "shell script" to do the actual work of generating the output file. I got the shell script from someone else and don't really know how it works.

You might also try de-authorizing and then re-authorizing your ADE account, which ought to generate a new ~/Library/Application Support/Adobe/Digital Editions/activation.dat file. That file contains the Private Key. My script (via the Unix shell script) accesses that Private Key within that file and puts it in the adeptkey.der file for subsequent use.

If you still need help, feel free to post whatever results you get to this thread, or else send me a private message ...

Cheers,
Eric

EDIT:

Or, try my earlier version:

link removed

I know version 1.1 works with 10.5 Leopard and has a problem with 10.6 Snow Leopard. Version 1.1a works with Snow Leopard, but maybe it sometimes fails with Leopard (even though it works on my copy of Leopard).

[evdberg]

Hi Eric,

The error comes after the selection window to choose the destination path and file. I also tried running the script itself, but that resulted in the same error. The message states the data is not base64. My guess is that the script can not find the key and is trying to use something else as key (hence the error message). How should that activation.dat file look like and where is the key located? Maybe I can then manually see what is the problem.

Thanks,
Erwin

[epstewart]

Originally Posted by evdberg

Hi Eric,

The error comes after the selection window to choose the destination path and file. I also tried running the script itself, but that resulted in the same error. The message states the data is not base64. My guess is that the script can not find the key and is trying to use something else as key (hence the error message). How should that activation.dat file look like and where is the key located? Maybe I can then manually see what is the problem.

Thanks,
Erwin

Ervin,

Here is my own activation.dat file:

http://epstewart.home.comcast.net/activation.dat

There are <privateLicenseKey></privateLicenseKey> tags in it. In between is the key itself, which I believe corresponds to the one that may be messed up in your case. However, be aware that this is my key and will not work on anyone else's computer, since it is tied to the computer and user log-in of the Adobe Digital Editions user — me — that created it when he authorized ADE.

You can inspect ~/Library/Application Support/Adobe/Digital Editions/activation.dat on your Mac, in the ~/ hierarchy for your log-in account. Maybe you can see what the problem is.

I can't quite imagine why there is a complaint about "not being base-64," since I believe any string of bits can be interpreted as being base-64! Perhaps the problem is one of the length of the string not being appropriate to a string of base-64 digits. I.e., base-64 digits require 6 bits per digit, so maybe your key's length in bits is not divisible by 6. (If you inspect the file in TextEdit, you should see a bunch of gobbledygook between the <privateLicenseKey></privateLicenseKey> tags. Keep in mind that TextEdit is "seeing" 8-bit bytes, i.e., ASCII code.)

Anyway, have you tried just de-activating and re-activating your account in ADE? I would trash your activation.dat file if it's still present after the de-activation, then re-activate, thus generating a new activation.dat file to use with the script. Or, create a new user account on your Mac and activate ADE under that account, and then see if the script works under that account.

Good luck ...


Eric

[epstewart]

Originally Posted by dynabook

I have installed the Developer Tools and the package

http://tmrc.mit.edu/mirror/twisted/D....5_osx10.5.pkg PyCrypto 2.0.1 for OS X 10.5

I get the error:

This script requires PyCrypto, which must beinstalled separately. Read top-of-script comment for details.

Any help? New to Mac, old hand at PC.
--MH

Try trashing the /Library/Frameworks/Python.framework/Versions/2.6/ folder and then reinstalling Python 2.6 and PyCrypto, in that order. It worked for me ...

Eric

[evdberg]

@Eric,
My activation.dat file is slightly different: a lot of tags have "adept:" in the tag name, for instance:

<adept:privateLicenseKey>

I will make a backup of the activation.dat file and remove the adept: part from the tag and see if it works.

You are wrong on base64: as the name suggests it encodes using 64 characters (6 bits at a time). Any other of the 64 selected characters is wrong and will give the mentioned error.

Update: Success!! I was able to extract the key and decrypt a book.

- Erwin