New version of DRM removal tools ("DeDRM")

[birdbrainbb]

Originally Posted by badgoodDeb

I'm familiar with only the concept of Git (used it for some code I modified). Wasn't the tree manager.

Is there a "download just the executable" right now, or do I have to request the whole source code tree? I just want to run the non-LCP code and don't care about what's inside it.

The sidebar on the right has the current release in a zip file, and if you download that you should be able to add it to Calibre per usual.

Here's the actual page: https://github.com/noDRM/DeDRM_tools...es/tag/v10.0.2

[badgoodDeb]

Ahh - thanks. It's on the bottom for me, not a sidebar. But your assurance that it existed made me look further down, I guess.

[Karellen]

Originally Posted by badgoodDeb

I'm familiar with only the concept of Git (used it for some code I modified). Wasn't the tree manager.

Is there a "download just the executable" right now, or do I have to request the whole source code tree? I just want to run the non-LCP code and don't care about what's inside it.

Are you after the zip download? You can grab that here...
https://github.com/noDRM/DeDRM_tools/releases

The zip install file is inside the downloaded zip file.

[badgoodDeb]

Thank you both! Now I'll sit on the zip file for a while until I decide to try an install (I'm on a several years old version now) but at least I have it.

[JSWolf]

Originally Posted by darryl

To me LCP is no big deal. I remain unaffected. I don't like DRM. I don't want to see an additional widespeard system including LCP. On the other hand, I find it hard to get too perturbed about a system which is overwhelmingly used to protect library books, at least so far.

So if your library switched to LCP DRM, you'd be OK with that when you can no longer read library eBooks on the device of your choice?

[JSWolf]

Originally Posted by darryl

The good news is that it seems noDRM has been able to have the repository reinstated with the offending parts removed.

Yes, that is good news. It means the DeDRM plugin can continue to be updated to go along with changes in Calibre and other changes can be made to keep it working.

[rantanplan]

Originally Posted by JSWolf

So if your library switched to LCP DRM, you'd be OK with that when you can no longer read library eBooks on the device of your choice?

What makes you think that Kobo and Amazon won't update their devices when this becomes relevant, just like European vendors did? LCP is software, not hardware.

[Ocipus]

Amazon have its own DRM with KFX. They don't support Adept or ePub.
So, I think, they don't update for LCP.

[DNSB]

Originally Posted by rantanplan

What makes you think that Kobo and Amazon won't update their devices when this becomes relevant, just like European vendors did? LCP is software, not hardware.

Considering that Kobo is responsible for the Tolino ereaders, they already have the LCP decryption code.

[PeterT]

Originally Posted by DNSB

Considering that Kobo is responsible for the Tolino ereaders, they already have the LCP decryption code.

But remember, their real focus is on Kobo supplied ebooks, and library materials fulfilled via the Kobo store. I doubt we'd see any support from them without an update to the RMSDK version that they use, and I sense that update is in itself problematic.

Sent from my Pixel 4a using Tapatalk

[darryl]

Originally Posted by JSWolf

So if your library switched to LCP DRM, you'd be OK with that when you can no longer read library eBooks on the device of your choice?

A logical question. No, I wouldn't like it. Reading on the device of my choice is very important to me. Whilst I was a member of a US library I was able to read on my Kindle. Now Now my US library could not renew my membership I'm stuck with Australian libraries. I read these books on my Kobo. I think there is quite a good prospect of Kobo supporting LCP if there is a demand for it. I'll worry about this if and when it does happen. In the meantime I can take comfort in the fact that the code is still out there and a choice available.

[JSWolf]

Originally Posted by darryl

A logical question. No, I wouldn't like it. Reading on the device of my choice is very important to me. Whilst I was a member of a US library I was able to read on my Kindle. Now Now my US library could not renew my membership I'm stuck with Australian libraries. I read these books on my Kobo. I think there is quite a good prospect of Kobo supporting LCP if there is a demand for it. I'll worry about this if and when it does happen. In the meantime I can take comfort in the fact that the code is still out there and a choice available.

Given Readium's hostile take down, I can easily see them changing the DRM just enough for the existing code to fail.

[ratinox]

Originally Posted by JSWolf

Given Readium's hostile take down, I can easily see them changing the DRM just enough for the existing code to fail.

Again, doesn't work that way, but for different reasons. Explaining why would be a dive into how AES-256 and asymmetric key management work, and this isn't the place.

[shalym]

Originally Posted by ratinox

Again, doesn't work that way, but for different reasons. Explaining why would be a dive into how AES-256 and asymmetric key management work, and this isn't the place.

Are you sure? Amazon is doing exactly that with the encryption attached to the KFX format. Every time it is cracked, the encryption changes, usually within 24 hours.

Shari

[darryl]

Originally Posted by JSWolf

Given Readium's hostile take down, I can easily see them changing the DRM just enough for the existing code to fail.

They may well do so, though personally I doubt they will bother. And if they do, someone will not be able to resist the challenge. New code will circulate privately and become more and more widespread.

Interestingly enough i didn't see the tone of the takedown as being particularly hostile. Unlike many such notices, it was very specific and in some ways almost conciliatory. It specifically excluded Apprentice Harper's repository, specifically acknowledging that readium was not not affected by it. It also went to some lengths to try to take the moral high ground with its arguments about library books. It also specifically referred to noDRM's future plans which it found threatening. Now, despite calling for hte removal of the repository, it seems to at least not be making waves now the readium code has been removed.

Having said this, it clearly does find the prospect of widely available trivially easy de-drm of LCP very threatening indeed to its business model at a time when it is trying to expand and compete aggressively with Adobe. As such I think we can expect aggressive action against any attempt to reinstate LCP to the tools or against any other entity who offers similar trivially easy functionality. I doubt readium will be all that bothered by the present situation nor do I think there is any action it can take which will materially improve its position.

I'm simply happy that this DRM infection is not more widespread.