I am running Windows 7 Ultimate 64 bit on an early dual core AMD chip with an NVidia AMD 590-SLI chipset. I have a Sony 600 Reader and wished access to Kindle's store library as well as Sony's so your script is perfect. txt tacked on the end, and when I do look at Unswindle.pyw in Windows Explorer, it's showing as a Python file (31KB).Īny thoughts where I'm going wrong? Thanks for your help! Reply Delete I've checked that the file isn't getting a. I'm taking the Raw script, for v6, from the link at the top of the page, copy/pasting the entire script to Note Pad, saving the file as Unswindle.pyw, using UTF-8 encoding. I did de-drm an ereader (pdb) format book, using the eReader2html.py script, to ensure that my Python installation was not corrupted/had issues, and the eReader2html.py ran without a problem and decrypted my book. This is the most response I've received when running the script it just seems to collapse after I try to execute (I've checked the processes running on my system after trying to execute, to ensure that it wasn't running the background, and I don't see the script, or Python itself, running.) Consistently, using Pythonw gives no response that I can see. Synta圎rror: EOL while scanning string literal We'll see if Amazon throws out another new build in short order, and I'll put some more elbow grease into figuring out the PID-generation algorithm.Īnonymous Decemat 8:09 Cabbage, I tried the command line that you suggested, but received the same results as earlier the Command Window in the window header did briefly (briefly!) flash up Pythonw.exe Unswindle.pyw, but no further results.Ĭ:\Python26>Python.exe Unswindle.pyw (or Unswindle.py) In any case, I've updated unswindle to handle the 20091222 version of the executable.
#Kindle for pc 64 bit update
The K4PC update may not actually have been targeted at unswindle, as Amazon seems to have done nothing in particular to make the basic approach more difficult. Newest unswindle version detects if you have the wrong K4PC executable installed. As you can clearly see via their SHA-1 hashes: fd386003520f7af7a15d77fcc2b859dd53e44bc1 KindleForPC-installer-20091217.exeġ3a816a3abf7a71e7b6a55228099b03b1dc3789b KindleForPC-installer-20091222.exeThe application doesn't seem to auto-update, so if you can find a copy of the original installer you should be fine. Amazon has demonstrated that they (unlike Adobe) take their DRM seriously: they've already pushed out a new version of K4PC which breaks this particular script. Version 6 cleanly handles already DRM-free files. Version 5 works with the new (20091222) version of the K4PC executable. Version 4 fixes an exception related to opening thread handles, detect Topaz format books, and detects that you have the proper version of Kindle For PC installed. Version 3 fixes an intermittent path-getting issue. It came to my attention that unswindle version 1 did not work if KindleForPC was installed as a non-administrator and did not work on versions of Windows other than XP.
Don't use this to steal, or I'm taking my toys and going home. Script name in honor of rms and The Right to Read. Put those kids together (in the same directory) and run unswindle.pyw. You'll also need a copy of darkreverser's mobidedrm (check the most recent comments for the newest links). So here you go: unswindle v7 (previous versions: v6 v5 v4 v3).
Way to go Amazon! It's good enough that I got bored unwinding it all and just got lazy with the Windows debugging APIs instead. And they seem to have done a reasonable job on the obfuscation. K4PC uses the same encryption algorithms, but ups the ante with a per-book session key for the actual en/decryption.
The Kindle proper and Kindle for iPhone/iPod app both use a single "device" encryption key for all DRMed content. Amazon actually put a bit effort behind the DRM obfuscation in their Kindle for PC application (K4PC).
0 kommentar(er)
