Adobe ADEPT DRM for EPUB circumvented

[66sprite]

Originally Posted by simplyparticular

I was able to get both books converted on my Mac by:

1. zipping the epub (right click, select compress)
2. unzipping it with built-in mac utility
3. rezipping it with pdurrant's AppleScript

Thanks to JSWold, trowley's PM and karma all around.

K, I will try again and see if I can get it to work.

[66sprite]

I followed the instructions and still got the error.

I decided to start over again and re-downloaded the scripts and this time it worked.

Everyone thanks for everything.

[DaleDe]

Originally Posted by spec

I wonder who needed to protect their author/publisher rights and put the DRM on almost 500 year old translation of the Bible? (rhetorical question)

Any book that is translated gets a new copyright owned by the one (company) doing the translation. The Bible you chose was a recent translation. However, all books work this way, not just Bibles.

[spec]

Originally Posted by DaleDe

Any book that is translated gets a new copyright owned by the one (company) doing the translation. The Bible you chose was a recent translation. However, all books work this way, not just Bibles.

I'm pretty sure that's not exactly how it works. by example: if I translate wikipedia to say, klingon, and start selling it, I cannot disregard original creating commons license, I would have to honor it. I also cannot just take "davinci code" or "angels and deamons", translate it to, say, klingon and "own copyright" on that translated book. I'm pretty sure my best bet would be to assume a suit coming in both instances (latter instance is more likely).

I just think it's a bit more complex. translator(s) get their due credit, but they cannot disregard the rights of the original author(s) and the license on which the work was released.

Sorry to start this off-topic discussion. It's just I think that with migrating to ebook as a new media of written word we as readers are loosing a lot of rights. And on top of that we see those completely ridiculous things like DRM put on public domain works

[DaleDe]

Originally Posted by spec

I'm pretty sure that's not exactly how it works. by example: if I translate wikipedia to say, klingon, and start selling it, I cannot disregard original creating commons license, I would have to honor it. I also cannot just take "davinci code" or "angels and deamons", translate it to, say, klingon and "own copyright" on that translated book. I'm pretty sure my best bet would be to assume a suit coming in both instances (latter instance is more likely).

I just think it's a bit more complex. translator(s) get their due credit, but they cannot disregard the rights of the original author(s) and the license on which the work was released.

Sorry to start this off-topic discussion. It's just I think that with migrating to ebook as a new media of written word we as readers are loosing a lot of rights. And on top of that we see those completely ridiculous things like DRM put on public domain works

You are right. I did oversimplify since the original copyright rules do have influence on the outcome but the Bible is pre-copyright laws although the original KJV is now under permanent copyright in the UK as is Peter Pan. Public Domain is a default condition after the copyright expires and is not the original authors intent normally. I suspect a translator can even copyright a document he/she created even if the original user released it in public domain. Public Domain means you can do anything you want with the document with no rights reserved by the original author. So you can legally even add DRM if you want to.

Dale

[FlorenceArt]

Originally Posted by ngrant

I had the same problem and found this solution on another website that worked for me. I downgraded my ADE to 1.7.1 as per the instructions (see below), then ran the first script ineptkey.pyw to create the adeptkey.der file which I have saved in the same folder as my epub books (and backed up safely elsewhere) and it still works even though I upgraded Digital Editions to the latest version afterwards. KEEP THIS KEY FILE SAFE and DO NOT RUN THE ineptkey.pyw EVER AGAIN! It will replace your working key with a non-working version.

Then go ahead and run the ineptepub.pyw script on each book one at a time to decrypt. I can't tell you how GOOD it felt the first time I was successful with this, after months of messing around with it. I can now read my Sony store ebooks on my jetBook Lite instead of my laptop and it is GLORIOUS.

Hope this helps you as it did me; copy or print these instructions as this post may have to be taken down by the mods for violating something or other...

Hello,

I just found out I have the same problem: I upgraded to ADE 1.7.2 and ran the script to get the key again, thinking it was the right thing to do. Apparently not

Problem is, I can't find a link to ADE 1.7.1 for Mac. Any suggestion?

[FlorenceArt]

Originally Posted by FlorenceArt

Hello,

I just found out I have the same problem: I upgraded to ADE 1.7.2 and ran the script to get the key again, thinking it was the right thing to do. Apparently not

Problem is, I can't find a link to ADE 1.7.1 for Mac. Any suggestion?

OK, forget I asked. I think I've got the answer. There is a new version of the ineptkey script (v4.3 or thereabouts), and most importantly for me a new script that actually works on Mac, it's called ineptkeymac. It seems to be working for now (crossing fingers).

Anyway, those new scripts can get the key from new versions of ADE, so I didn't need to find and install an old version. Phew. I'm actually going to be able to read the book I bought.

[ngrant]

Hi FlorenceArt, I was going to suggest that you try the new tools available for the latest version of ADE, so I'm glad that you got it to work. I have been able to decrypt all my DRM epubs so far with my "old" key so am not going to touch or "upgrade" anything to cause it to stop working, ha ha. This works so well for me that I stopped purchasing any other format, like secure ereader -- which works on my jetBook Lite BUT what if I get another device that does not do pdb?? Another round of conversions? No thanks. I'm happy to unlock the epub format and hope that it is indeed the "standard" format of the future which will work on any device.

[The Old Man]

Thanks for the help with my problem.

[fakename1024]

Originally Posted by thename

I was able to successfully retrieve a key via Wine but it took a bit of jiggering the locations. Installed Python and PyCrypto for Windows in Wine. Then ran the script in a separate desktop via:

wine explorer /desktop=name,1024x768 python.exe ineptkey.py

What a relief; wasn't ready to get my Windows box back up just to regenerate a stupid key!

That didn't work for me. Here's what I did that worked:


<<MODERATED.... Step but step instructions and links to DRM removal tools are not allowed.>>

[Toxaris]

I am not quite sure, but I think that a link to the python scripts is not allowed here on the forum. Please remove them to avoid complications. Mentioning the scripts is allowed.

[astra]

One time is enough to get all the info

[NookyBook]

After using INEPT on an epub there remains a string on every file in the epub.

The string is:
<meta name="Adept.resource" value="urn:uuid:a43f58df-6769-422f-a57f-f0afa42fe7a6"/>

This is distinct from and in addition to the uid ISBN that is used in the epub. The string is in the header of every xml/html content file in the epub.

Is this urn:uuid a benign number, or can it be used as part of the ADEPT DRM to track down the origination of the download, purchaser, or the machine of the originator? Is it a bloody fingerprint?

[pdurrant]

Originally Posted by NookyBook

After using INEPT on an epub there remains a string on every file in the epub.

The string is:
<meta name="Adept.resource" value="urn:uuid:a43f58df-6769-422f-a57f-f0afa42fe7a6"/>

This is distinct from and in addition to the uid ISBN that is used in the epub. The string is in the header of every xml/html content file in the epub.

Is this urn:uuid a benign number, or can it be used as part of the ADEPT DRM to track down the origination of the download, purchaser, or the machine of the originator? Is it a bloody fingerprint?

Frankly, who cares? It doesn't stop you using the file for any legitimate purpose.

[ATimson]

Originally Posted by pdurrant

Frankly, who cares? It doesn't stop you using the file for any legitimate purpose.

It's theoretically possible that an Adobe SDK reader (Digital Editions, txtr on iPhone) could phone home those tags, leading to the disabling of the Adobe account of anybody who used INEPT.

Likely, no; paranoid, yes. But still possible.