Readium: Difference between revisions

Line 69:

As well as that the explicit circumvention of Readium LCP was in a file called '''"lcpdedrm.py'''." And that: <blockquote>"The user noDRM is actively promoting the activity of cracking both library loans and one-off purchases"</blockquote>followed to a link to a GitHub Issue to substantiate the claim.<ref>{{Cite web |title=2022-01-04-readium |author=[private] |date=2022-01-04 |url=https://github.com/github/dmca/blob/master/2022/01/2022-01-04-readium.md |url-status=live |archive-url=https://web.archive.org/web/20260604153156/https://github.com/github/dmca/blob/master/2022/01/2022-01-04-readium.md |archive-date=4 Jun 2026 |access-date=23 Jun 2026}}</ref>

As a result, the relevant files as well as relevant [[wikipedia:Git|Git]] history was removed from the repository.<ref>{{Cite web |author=captn3m0 |date=17 Mar 2025 |title=Extracting content from an LCP “protected” ePub |url=https://news.ycombinator.com/item?id=43378627 |url-status=live |website=news.ycombinator.com |archive-url=https://web.archive.org/web/20260616102133/https://news.ycombinator.com/item?id=43378627 |archive-date=16 Jun 2026 |access-date=24 Jun 2026}}</ref>

===Response to a Published Circumvention Method (2025)===

In March 2025, a [[wikipedia:Mastodon (social network)|Mastodon]] user called Terrence Eden made a post about circumventing Readium LCP, and later described his method in a blog post. Shortly after, he reportedly received a [[LinkedIn]] message from somebody at the Readium Foundation. The person "congratulated" Eden and mentioned that: <blockquote>"We managed to convince publishers (even big US publishers) to adopt a solution that is flexible for readers and appreciated by public libraries and booksellers.

Our gains are re-injected in open-source software and open standards (work on EPUB and Web Publications).

If the DRM does not succeed, harder DRMs (for users) will be tested.

I let you think about that aspect"</blockquote>In a response, Eden stated that the his method was basic, used the app's built-in debugging functionality and that he had not reverse engineered their app or decrypted their secret keys. He stated that he would publish his research and the correspondence, but that he wouldn't publish any of their intellectual property. Their reply included what Eden in his blog described as a "crude attempt at emotional manipulation."<blockquote>"We were planning to now focus on new accessibility features on our open-source Thorium Reader, better access to annotations for blind users and an advanced reading mode for dyslexic people. Too bad; disturbances around LCP will force us to focus on a new round of security measures, ensuring the technology stays useful for ebook lending (stop reading after some time) and as a protection against oversharing.

You can, for sure, publish information relative to your discoveries to the extent UK laws allow. After study, we'll do our best to make the technology more robust. If your discourse represents a circumvention of this technical protection measure, we'll command a take-down as a standard procedure."</blockquote>The correspondence came to a close after Eden's reply:<blockquote>"As you have raised the possibility of legal action, I think it is best that we terminate this conversation."</blockquote><ref name="eden" /><ref name="eden"/><ref>{{Cite web |author=Terrence Eden |date=Mar 2025 |title=114155981621627317 |url=https://mastodon.social/@Edent/114155981621627317 |url-status=active |website=mastodon.social |archive-date=24 Jun 2026 |archive-url=}https://web.archive.org/web/20260624093517/https://mastodon.social/@Edent/114155981621627317}</ref>

(Refer to [[Readium#External Links|External Links]] for the entire correspondence.)

==Products==

@@ Line 69: / Line 69: @@
 As well as that the explicit circumvention of Readium LCP was in a file called '''"lcpdedrm.py'''." And that: <blockquote>"The user noDRM is actively promoting the activity of cracking both library loans and one-off purchases"</blockquote>followed to a link to a GitHub Issue to substantiate the claim.<ref>{{Cite web |title=2022-01-04-readium |author=[private] |date=2022-01-04 |url=https://github.com/github/dmca/blob/master/2022/01/2022-01-04-readium.md |url-status=live |archive-url=https://web.archive.org/web/20260604153156/https://github.com/github/dmca/blob/master/2022/01/2022-01-04-readium.md |archive-date=4 Jun 2026 |access-date=23 Jun 2026}}</ref>
 As a result, the relevant files as well as relevant [[wikipedia:Git|Git]] history was removed from the repository.<ref>{{Cite web |author=captn3m0 |date=17 Mar 2025 |title=Extracting content from an LCP “protected” ePub |url=https://news.ycombinator.com/item?id=43378627 |url-status=live |website=news.ycombinator.com |archive-url=https://web.archive.org/web/20260616102133/https://news.ycombinator.com/item?id=43378627 |archive-date=16 Jun 2026 |access-date=24 Jun 2026}}</ref>
+===Response to a Published Circumvention Method (2025)===
+In March 2025, a [[wikipedia:Mastodon (social network)|Mastodon]] user called Terrence Eden made a post about circumventing Readium LCP, and later described his method in a blog post. Shortly after, he reportedly received a [[LinkedIn]] message from somebody at the Readium Foundation. The person "congratulated" Eden and mentioned that: <blockquote>"We managed to convince publishers (even big US publishers) to adopt a solution that is flexible for readers and appreciated by public libraries and booksellers.
+Our gains are re-injected in open-source software and open standards (work on EPUB and Web Publications).
+If the DRM does not succeed, harder DRMs (for users) will be tested.
+I let you think about that aspect"</blockquote>In a response, Eden stated that the his method was basic, used the app's built-in debugging functionality and that he had not reverse engineered their app or decrypted their secret keys. He stated that he would publish his research and the correspondence, but that he wouldn't publish any of their intellectual property. Their reply included what Eden in his blog described as a "crude attempt at emotional manipulation."<blockquote>"We were planning to now focus on new accessibility features on our open-source Thorium Reader, better access to annotations for blind users and an advanced reading mode for dyslexic people. Too bad; disturbances around LCP will force us to focus on a new round of security measures, ensuring the technology stays useful for ebook lending (stop reading after some time) and as a protection against oversharing.
+You can, for sure, publish information relative to your discoveries to the extent UK laws allow. After study, we'll do our best to make the technology more robust. If your discourse represents a circumvention of this technical protection measure, we'll command a take-down as a standard procedure."</blockquote>The correspondence came to a close after Eden's reply:<blockquote>"As you have raised the possibility of legal action, I think it is best that we terminate this conversation."</blockquote><ref name="eden" /><ref name="eden"/><ref>{{Cite web |author=Terrence Eden |date=Mar 2025 |title=114155981621627317 |url=https://mastodon.social/@Edent/114155981621627317 |url-status=active |website=mastodon.social |archive-date=24 Jun 2026 |archive-url=}https://web.archive.org/web/20260624093517/https://mastodon.social/@Edent/114155981621627317}</ref>
+(Refer to [[Readium#External Links|External Links]] for the entire correspondence.)
 ==Products==