Quote:
Originally Posted by DaleDe
One of the problems is that if you tell everyone how you did it then it compromises the security of the method.
Dale
|
Most of the ideas mentioned in this thread have been tried out already. The second layer of defense in any DRM'ed document are these telltales, which exist in jpeg, opf, html, xml, and css files. I have a theory about why Adobe and Amazon made it so easy for their DRM schemes to be broken. It's because they stuck enough telltales into the files to trace it back to the source recipient, who was then dumb enough to post it on the internet. OK, maybe I'm giving Adobe too much credit. It could be that they really are negligent. The next revisions of ADE and Amazon's Kindle for PC should be very interesting.
In the html files, I'm waiting to see if an author tries adjusting the words between the <p> and </p> paragraph tags, using ordinary line feeds to vary the count of words per line in the ascii file. And to do it "uniquely" per delivered file. Such a change would be totally transparent to any ereader, and might even look natural to someone editing the raw html. Of course, this scheme is easily defeatable.
The OP has been exposed to a number of good ideas by this board, and let's hope he can get back to us in a few months to see if he caught a pirate distributor at work.