Extracting content from an LCP "protected" ePub
shkspr.mobi
As Cory Doctorow once said "Any time that someone puts a lock on something that belongs to you but won't give you the key, that lock's not there for you." But here's the thing with the LCP DRM scheme; they do give you the key! As I've written about previously, LCP mostly relies on the user entering their password (the key) when they want to read the book. Oh, there's some deep cryptographic magic in the background but, ultimately, the key is sat on your computer waiting to be found. Of…

Finally there are some more methods to tackle LCP DRM, but the messages to the creator from Readium consortium is so frustrating. Just read this:

“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.”

Also on Mastodon

  • notanapple@lemm.eeEnglish
    1·
    19 days ago

    I might be in minority here but I kinda see the point the Readium guy is making, specifically this one:

    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

    Publishers and companies will always want DRM so at the very least we (as a community) could offer a DRM that is less flawed, more respecting of privacy and FOSS, etc. If we dont, someone else will offer a DRM solution thats far worse (and publishers will implement it because they dont care and there are no consequences).