Quote:
Originally Posted by Jim Lester
DRM is always undocumented.... jeez  We use a particular variant of Adobe DRM ('Passhash') that nobody else has picked up... yet. |
Fair enough. I was expecting something more documented in the same way that crypto algorithms (etc) are documented.
Quote:
Originally Posted by Jim Lester
If you want to know which variant of Adobe DRM then:
rights->licenseToken->user will not exist with Passhash based DRM (that we use for Trade), but will with ACS4 Classic licenses (that we use for Education).
If you want to know where you got the book from then operatorURL is your best bet f, but if the back end server is in a middle man role this won't work as well. For instance a book that I get from the San Jose Public Library will have an Overdrive or NetLibrary operatorURL, and not a San Jose Public Library URL. (There are similar arrangements for purchasing).
|
Terrific stuff, thanks Jim! The books I've just checked do all have rights>licenseToken>user so must all be ACS4-ish "Classic" licenses.
Another thought. Do the adept:certificate elements in B&N books still have an X.509 certificate? The ones in the Adept DRMed books I've got here all seem to, and have a subject name of "cn=https://nasigningservice.adobe.com/licenses,ou=Digital Publishing,o=Adobe Systems Incorporated,c=US"
I just grabbed a book from our local (Overdrive) library and it had:
<licenseURL>https://nasigningservice.adobe.com/licensesign</licenseURL> <operatorURL>http://acsepub.contentreserve.com/fulfillment</operatorURL>
(and the same Adobe X.509 certificate)
Nothing really useful there... But the permissions>display>loan/until elements might be another interesting thing to display.