Thread: Hacks kindlepid/kindlefix 0.2
View Single Post
Old 03-11-2009, 05:41 PM   #70
tompe
Grand Sorcerer
tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.
 
Posts: 7,452
Karma: 7185064
Join Date: Oct 2007
Location: Linköpng, Sweden
Device: Kindle Voyage, Nexus 5, Kindle PW
Quote:
Originally Posted by InlawBiker View Post
Eh, well, I'm not a lawyer but I know a bit about cryptography and programming. I changed the script so I don't always have to type my PID and now I'm digging into the code. The DRM is not circumvented, removed or altered with kindlefix.py. The payload (the e-book) is still encrypted and usable only by the PID(s) used to encode it.
The meta data is changed and it is not encrypted. What I do not understand is why people comsider the encryption being the only part of the DRM. The bits that kindlefix.py changes is also part of the DRM system.

If it legally is not effective then this is one thing. It is still part of the DRM event if it is not legally effective.
tompe is offline   Reply With Quote