DRM is not being removed: Calibre 4.23/DeDRM6.8/Kindle for Mac 1.26.1/Mac Big Sur #1369
Comments
|
Was the book downloaded with the current installation of Kindle for Mac located on the same machine and user as calibre with DeDRM? |
|
Yes. But not the "current" installation of Kindle for Mac. It was version 1.26.1 |
|
For some reason, DeDRM is unable to decrypt the key that it is finding. Possibly something left behind from a previous installation. Try deleting this file: /Users/lisa/Library/Application Support/Kindle/storage/.kinf2018 |
|
So I decided to just delete everything and start over. I uninstalled Kindle, Calibre, deDRM plugin. (I also deleted that entire Kindle folder under Application Support (and anywhere else I found Kindle App items).
Calibre Log |
|
And you redownloaded the book after this new installation? And added the fresh copy to calibre? |
|
Yes, I deleted from Calibre, deleted from My Kindle Library and redownloaded... multiple times. |
|
I also have all these same versions installed on a MacBook running Catalina, and it all works fine. I'm suspicious that it has something to do with Big Sur. |
|
Do you have KFX downloads disabled? |
|
I think so. If you mean, running: Then yes. If not, then probably not. |
|
Yes, that's what I meant. I don't know what else to suggest. Seems like it might be something to do with Big Sur. But I have no idea. |
|
Are you one of the developers? If not, are they monitoring this thread? More and more users will be upgrading to Big Sur. Seems like this might be something they'd want to look into. I'm willing to try any other ideas to help debug this including (but not limited to), uninstalling, reinstalling, changing up the order of steps, etc. |
|
I'm not. As you say, I'm sure there will be more reports if Big Sur is the issue, and @apprenticeharper and company will become aware. I will also ask around myself. |
|
I tried posting to mobileread, but they closed it immediately. I didn't even post instructions, I just spoke about the problem in the abstract. I don't know where else to post to see if others are having the same issue. |
|
Yeah, I think they were a little overzealous with that. Hopefully we get some responses from the other thread there. |
|
|
|
Saving the keys from my MacBook running Catalina and importing them to my Mac mini running Big Sur did not work: If I click the plus sign, I get this error: So the problem seems to lie with the non-existence of the proper keys. Maybe @apprenticeharper can offer some help? |
|
DeDRM will only automatically save a key that successfully decrypted a book. So that's why nothing was there at first. I think the error message you got when trying to add the key may be because DeDRM is not able to decrypt the key, not because it can't find one at all. At least that's what the log from importing a book seemed to indicate. And the key for each installation of the Kindle is unique (even a reinstallation on the same machine which requires you to login again can change the key). So that's why the keys from your Catalina don't work on books from the Big Sur Kindle app. I'd be curious to see if you could decrypt a book from the Catalina Kindle app with the Big Sur calibre/DeDRM setup with the Catalina's imported keys. |
|
Ha! So that worked. So how do we get the proper keys for Big Sur??? |
|
Therein lies the problem. It appears that DeDRM can't decrypt the key for the Big Sur installation of the Kindle app. It's beyond my knowledge of this to see why. But at least that might narrow the issue for those who can figure it out. |
|
If I use the "download via usb" method, it all works fine! TBH, that's easier anyway. |
|
Ah, didn't know you had an E-ink Kindle. This will still need looking at, but at least book decryption seems fine with Big Sur. It's just getting and decrypting the key for Kindle for Mac that is giving trouble. |
|
Thanks for all your help. If and when someone has time to fix this, just @ me or something and I'll be happy to test it. |
|
Patch kindle for mac catalina and Big Sur with following command, |
|
Remember that you have to do this every time the Kindle app is upgraded.
…On 11/24/20 9:16 PM, Augilare wrote:
Patch kindle for mac catalina and Big Sur with following command,
chmod -x /Applications/Kindle.app/Contents/MacOS/renderer-test
OR
sudo chmod -x /Applications/Kindle.app/Contents/MacOS/renderer-test,
Then right-click kindle book to download. DON'T double click or open
it before the drm removing.
Convert Kindle KFX to EPUB/PDF Free on macOS Big Sur (Effective)
<https://garydadic.medium.com/convert-kindle-kfx-to-epub-pdf-free-on-mac-10-15-catalina-included-7ea1d7d2b609>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1369 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWVX7LZDYKDEQFUF2PZNLDSRSOKJANCNFSM4T4K6REA>.
--
"There are more things in heaven and earth, Horatio,
Than are dreamt of in your philosophy. "
|
|
@Augilare |
|
@Lisa10101 — have you tried this with K4Mac 1.30? The blogger referenced by @Augilare reports success using Calibre 4.23, DeDRM 6.8, K4Mac 1.30 and Mac mini M1 Big Sur. |
|
@ZolaLa9 I have not tried 1.30, mostly because DeDRM 6.8 states it's not compatible with anything over 1.26. If I give it a try later, I'll report back. |
|
@Lisa10101 |
|
@Lisa10101 — This post is updated regularly and tends to have the most up-to-date info on K4Mac compatibility: https://www.mobileread.com/forums/showpost.php?p=3819708&postcount=508 Not sure how active you are on MobileRead, but there is also active discussion happening here on DeDRM 7.0 beta and Mac: https://www.mobileread.com/forums/showthread.php?s=32fb948c4aa246ac91444f4a00ca6632&p=4061946#post4061946 |
|
I'm not interested in installing things that are "beta" or "in development", so I felt this was the better place to look for compatibility between DeDRM and Calibre:
and this:
|
|
And the next sentence:
But non-KFX formats can be decrypted from the later versions. |
|
@ElleKayEm It doesn't say "But non-KFX formats can be decrypted from the later versions." |
|
Have a look at this old issue #255. It seemed to be a similar issue with DeDRM not being able to decrypt the Kindle for Mac key. Sounds like the key encryption is tied to an ID number from the internal drive. Perhaps something with Big Sur or your particular setup is causing DeDRM to grab the wrong number. (DeDRM 6.8 addressed two things: decryption of the new Kindle for PC/Mac key which first appeared in version 1.25 and new KFX DRM used in versions 1.25-1.26. A further change to KFX DRM happened beginning with 1.27 which DeDRM does not handle yet. But the DRM on the older formats that you get when you disable KFX format downloads has not changed.) |
|
DeDRM uses a variety of cryptographic routines that do much of the same thing due to its history as a bunch of separate tools created by different individuals. I believe that the problem with Big Sur is caused by one of those no longer being available or having its named changed. This and others like it could be eliminated in favor of the cryptography library built into calibre. |
|
It looks like the plugin is failing to load See saltstack/salt#57787 for more info re: failing to load dylibs in Big Sur. It does seem like loading Calibre's version of OpenSSL would solve this once and for all, but I'm happy to put in a PR with the fix. |
|
@protochron — AWESOME!!! If you would put in a PR, it would be mucho appreciated! |
@Lisa10101 — Catalina + K4Mac 1.30 + Calibre 4.23 + Alf 6.8.0 = working for me |
|
I don't have Big Sur, and I'm still working on other Python 3 problems. A pull request that fixed this problem would be much appreciated. |
It looks like Big Sur removed `libcrypto.dylib` as a file on the filesystem, so loading it using `ctypes.find_library` fails which breaks Kindle decryption. Now to load a dylib you need to attempt to load it directly and the operating system will load the dylib from the OS' cache or fail. This fixes the problem by explicitly setting the path to libcrypto to `/usr/lib/libcrypto.dylib` if `ctypes.find_library` does not find the file, loading the dylib and raising an exception if it fails at that point. See saltstack/salt#5778 for more detailed info. Closes apprenticeharper#1369.
It looks like Big Sur removed `libcrypto.dylib` as a file on the filesystem, so loading it using `ctypes.find_library` fails which breaks Kindle decryption. Now to load a dylib you need to attempt to load it directly and the operating system will load the dylib from the OS' cache or fail. This fixes the problem by explicitly setting the path to libcrypto to `/usr/lib/libcrypto.dylib` if `ctypes.find_library` does not find the file, loading the dylib and raising an exception if it fails at that point. See saltstack/salt#5778 for more detailed info. Closes apprenticeharper#1369.
It looks like Big Sur removed `libcrypto.dylib` as a file on the filesystem, so loading it using `ctypes.find_library` fails which breaks Kindle decryption. Now to load a dylib you need to attempt to load it directly and the operating system will load the dylib from the OS' cache or fail. This fixes the problem by explicitly setting the path to libcrypto to `/usr/lib/libcrypto.dylib` if `ctypes.find_library` does not find the file, loading the dylib and raising an exception if it fails at that point. See saltstack/salt#5778 for more detailed info. Closes apprenticeharper#1369.
|
#1381 fixes the key finding/loading for me on Big Sur, though it still fails importing an |
|
I know this is an old thread but I had a similar issue with Catalina, kindle 1.26 and calibre 4 and 5. What Aguilare said not to actually click the book when downloading, helped me. It appears as soon as kindle opens the book it says preparing your book and deletes the azw format. Despite using kindle 1.26, updates disabled, updates folder removed, etc.
|
CheckList
The Titleand TheLog Titleare setted correctly.my environment.the log.Title
DRM is not being removed
My Environment
Calibre: 4.23
Kindle: 1.26.1
DeDRM: 6.8
Mac mini M1 Big Sur
Log
Removing DRM of Salt to the Sea
The text was updated successfully, but these errors were encountered: