New version of DRM removal tools ("DeDRM")

[odamizu]

Originally Posted by Lynx-lynx

Please note, it appears that with Kobo's latest desktop release they have changed their proprietory DRM. Therefore the latest Tools (or any version of the Tools containing 'obok') won't work.

Ouch. Can you still liberate Kobobooks if you go the epub route and download them via ADE? Or did they switch to Adobe's "hardened" DRM as well?

[Lynx-lynx]

Originally Posted by odamizu

Ouch. Can you still liberate Kobobooks if you go the epub route and download them via ADE? Or did they switch to Adobe's "hardened" DRM as well?

I bought Kobo epub books on Sunday (or Sat?) And didn't have any probs running through Calibre.

I haven't bought a book that was only available in kepub for a while now, and as I rarely use Desktop for PC I'm still using an older version.

It's a bit of a wait and see re identifying kepub programming changes and then addressing those through obok. The Friends of obok are aware, and so I think is Apprentice Harper because it's mentioned on github.

My suggestion is not to upgrade to v3.17.

For info, I've started a thread in the Kobo Devices sub forum.

[mbovenka]

Originally Posted by HarryT

How very odd! I wonder why?

So do I. I have an Analog subscription, and have my old DXG still registered to my account just for that. Now with the (easier) Android support, I can finally retire it. I've been playing with adb before, so I was in familiar territory.

But I agree, the K4PC route is easier.

[lkmiller]

FYI: Kobo Desktop for PC

I think the DRM is still the same, there's just some change in the program itself. I had an older version installed, and when I let it update from within the program, it only went to 3.15. I had to download the new setup file from the website to get 3.17. I uninstalled 3.17, reinstalled 3.15 (from my old setup file), and was back in business with Obok.

Not a big deal anyway since I haven't come across a kepub only file for a while now, and the Adobe DRM epubs haven't changed.

[Lynx-lynx]

@lkmiller did you try importing a kepub into Calibre from 3.17?

[AnemicOak]

Originally Posted by odamizu

Ouch. Can you still liberate Kobobooks if you go the epub route and download them via ADE? Or did they switch to Adobe's "hardened" DRM as well?

They're still using Content Server 4.0.3 for Adobe DRM so no new DRM. They'd need to be running at least CS 4.2 for that.

[JSWolf]

New version 6.3.3 of the DRM removal tools. 6.3.3 fixes a bug when first getting the Kindle for PC (or Kindle for Mac) key.

https://apprenticealf.wordpress.com/

[odamizu]

Originally Posted by Lynx-lynx

I bought Kobo epub books on Sunday (or Sat?) And didn't have any probs running through Calibre.

Originally Posted by AnemicOak

They're still using Content Server 4.0.3 for Adobe DRM so no new DRM. They'd need to be running at least CS 4.2 for that.

Oh good. Thank you!

[odamizu]

Originally Posted by pdurrant

I don't think there is any good basis for such assurance. Amazon have changed the encryption used in the various software implementations of Kindle readers several times. They've also worked hard to make hacking the hardware Kindles impossible via software.

But I do hope that Amazon won't do anything really silly.

<sigh> I agree on both counts.

[JSWolf]

Originally Posted by odamizu

<sigh> I agree on both counts.

Amazon has already done something really silly hence this new KFX format just for the enhanced typesetting when they could have had enhanced typesetting using KF8 eBooks with no change to them at all.

Adobe did it with RMDSK. They've included enhanced typesetting with no change to ePub eBooks at all. Amazon could have done the same thing. This is just another tactic to get users to buy/download from Amazon since doing otherwise would mean no enhanced typesetting.

[HarryT]

Originally Posted by JSWolf

Amazon has already done something really silly hence this new KFX format just for the enhanced typesetting when they could have had enhanced typesetting using KF8 eBooks with no change to them at all.

Adobe did it with RMDSK. They've included enhanced typesetting with no change to ePub eBooks at all. Amazon could have done the same thing. This is just another tactic to get users to buy/download from Amazon since doing otherwise would mean no enhanced typesetting.

You have absolutely no way of knowing what Amazon's reasons are for introducing a new file format or whether or not those reasons are "silly".

[JSWolf]

Originally Posted by HarryT

You have absolutely no way of knowing what Amazon's reasons are for introducing a new file format or whether or not those reasons are "silly".

Can you explain a need to come up with a completely new eBook format to support enhanced typesetting when we know it's possible to support enhanced typesetting with existing formats?

[HarryT]

Originally Posted by JSWolf

Can you explain a need to come up with a completely new eBook format to support enhanced typesetting when we know it's possible to support enhanced typesetting with existing formats?

I can think of all sorts of reasons. One might be that, given the fact that images appear to be stored in a separate "sidecar" file in the new format, they're now delivering books with image resolutions tailored to the capabilities of the specific device the file is being sent to. That would be a very smart move.

[JSWolf]

Originally Posted by HarryT

I can think of all sorts of reasons. One might be that they wanted to take the opportunity to introduce a more robust DRM mechanism due to the ridiculous ease of bypassing the old DRM.

Coming up with a new format is a way to handle the ease at which DRM removal and reverse engineering is possible with KF8/Mobi. But, that's silly. That means that Amazon has to convert all of their eBooks to KFX format when if they'd done the enhanced typesetting the sensible way, EVERY KF8 eBook sold by Amazon would have enhanced typesetting from day one of the firmware release.

[HarryT]

Originally Posted by JSWolf

Coming up with a new format is a way to handle the ease at which DRM removal and reverse engineering is possible with KF8/Mobi. But, that's silly. That means that Amazon has to convert all of their eBooks to KFX format when if they'd done the enhanced typesetting the sensible way, EVERY KF8 eBook sold by Amazon would have enhanced typesetting from day one of the firmware release.

Please see my edited post. I think the idea that they're now customising the images for the device that the device is being delivered to is far more likely. Ie have a core file that's delivered to all devices with the text of the book, and an auxiliary file containing images and other items that are device-dependent. We know that the book's image are now being delivered in a separate file and that fits in very well with Enhanced Typesetting.