The Readme file just said "post a comment in your blog. Hope I am posting this in an acceptable place. So you're really helping a very underserved segment of the population, though u probably didn't intend it so. Seems like most sighted folks think that everything's automatically translated into Braille, but the truth is that between talking books & braille, we only get about 3000 books a year, which is about the number of books that's put out in < a month. It's really unfair that materials which could be made accessible to us & which could broaden our reading possibilities are so restricted. Since by law in the United states blind people are in fact given permission to circumvent encryption technology that keeps us from reading, it's actually legal for me to do this. Because of your scripts, I'm able to buy & read books or borrow them from a digital library just like my sighted counterparts. In case u wonder how folks use your scripts-I'm blind, & apps put out by Barnes & Noble, Adobe, &, up until just a few days ago, Kindle, are completely inaccessible to screenreading technologies. I am currently running skindle, so this is not an emergency, but I would like to try unswindle. I did it all over again logged in as administrator, and got the same error messsge. I got this error message:įile "C:\Python26\unswindle.pyw", line 851, in gui_maininpath, pid = unswindler.get_book ()įile "C:\Python26\unswindle.pyw", line 792 in get_bookgrabber = PC1KeyGrabber(debugger, self._hexdigest)įile "C:\Python26\unswindle.pyw", line 652, in_init_t_bp(self._taddr(addr), getattr(self, mname))įile "C:\Python26\unswindle.pyw", line 461, in set_bpbyte = self.read_process_memory(addr, type=ctypes.c_byte)įile "C:\Python26\unswindle.pyw", line 451, in read_process_memoryraise DebuggerError ("could not read memory 0x%8x" % (addr,))ĭebuggerError: ciould not read memory 0x1000000000016591f
I renamed unswindle 7 and put it in Python26, where mobidedrm is located. Reply Deleteĭon't know where my question went, so excuse me if this is a double post. I'm not sure which, but I thought I would mention it here.
Vbk drm removal linux zip#
It could have been an accidental corruption that was never noticed because ADE doesn't pay attention to the zip file's directory - or it could have been a deliberate attempt to make life difficult for people using, ah, non-standard tools to manipulate the file. I manually unziped it, and unzip trusts the central directory more than the local/header filename, but it displays both, and after I manually renamed the file and rezipped it, ineptepub.py was able to decrypt it. Zipfile.BadZipfile: File name in directory "Tale_9780456pg" id="f085" media-gg" and header "Tale_978045606921_epub_opf_r1.opf" differ.Īdobe Digital Editions apparently only looks at the local/header filename, so it has no problem reading the file. This cause ineptepub.py to throw an exception: But a book I purchased from fictionwise had a deliberately corrupted entry for the. Whether it was deliberate or not, I can't say. The results was either no change at all or a python exception. I tried removing different blocks to see if it they changed what ineptkey.py did. I'm still not sure why I have three XML blocks in my activations.dat file, all with apparently different private keys and certificates. Yellow Bear Jat 4:08 Version 5.2 solved things for me as well. It should be fixed for versions 5.2 and beyond.
Vbk drm removal linux mac os#
Update - I had a bug in ineptepub which was causing segmentation faults on some versions of Mac OS X.
I am aware of skindle, but (a) one needs something like unswindle to run newer versions of K4PC under on Linux Wine anyway and (b) I think the unswindle UI is nicer, as one can't identify a particular K4PC book just by filename. If I missed a version or so in there, please try upgrading K4PC before complaining that it doesn't work.
I elected not to integrate the "bulk decryptor" ineptepub changes - my feeling is that anyone who needs bulk decryption can do it via the command-line.įor unswindle, I've just updated the tool to handle the most recently-released version of K4PC. These two changes should greatly simplify ADEPT EPUB DRM removal under OS X.
Vbk drm removal linux mac os x#
I did however (a) incorporate a version of the Mac OS X key-extraction logic into ineptkey and (b) allow ineptepub to use OpenSSL instead of P圜rypto, removing the need to install P圜rypto on OS X. Nothing terribly new, but I've updated ineptkey & ineptepub and unswindle.įor the INEPT tools I mostly just integrated and cleaned up the changes made by others.
0 kommentar(er)
