981

DRM removal tool was taken down from github. If you can, please download it from gitlab before its taken down too (merv.news)

submitted 1 year ago* (last edited 1 year ago) by nix@merv.news to c/piracy@lemmy.dbzer0.com

170 comments fedilink hide all child comments

The DRM removal tool to remove DRM from ebooks was taken down from github and will most likely be taken down from gitlab soon as well. The more archives we have the better so im sharing the gitlab in hopes some Datahoarder types will archive it and keep it shared via torrents etc https://gitlab.com/bipinkrish/DeGourou

Heres an article about why it was taken down https://torrentfreak.com/internet-archive-targets-book-drm-removal-tool-with-dmca-takedown-230714/

Edit: does anyone here use https://radicle.xyz/ ? Its a p2p network built on top of git and could be a good way to host it while still being able to contribute to it besides making a .torrent for archiving

you are viewing a single comment's thread
view the rest of the comments

[-] PolarisFx@lemmy.fmhy.ml 11 points 1 year ago

Amazon changed some things at the beginning of the year, they made it very difficult to get the actual file in azw format. They only let you download kindle unlimited books in their secure kfx(?) format, which current DRM removal plugins are unable to process.

If you buy the book you can goto Content & Devices and download the book in azw3 format which can be processed by the DRM removal plugin.

From what I've read amazon is monitoring the sites where they're developing kfx bypass mechanisms and are sealing up those holes before a public release can be made. Which is irritating because I just hate the Kindle app and prefer MoonReader

[-] sus@programming.dev 4 points 1 year ago* (last edited 1 year ago)

I'm pretty sure someone fully cracked kfx again - they just didn't bother to make it work for kfx directly - the newest form of azw is just zipped kfx from what I understand

about 3 weeks ago the solution was merged to the current big active deDRM fork. Amazon seems to only respond when the new workaround percolates to the big easy to use front-ends like calibri

(And I don't think the timeline for amazon sealing up the holes is actually all that fast. The original setup was being spread on some forums for several months now, and the january update from amazon was also quite "late")

also there's also several forms of downgrade attacks that mean only content released after amazon's latest fix becomes uncrackable