From: Apprentice Harper Date: Mon, 9 Mar 2015 07:38:31 +0000 (+0000) Subject: tools v6.2.0 X-Git-Url: http://git.xmof.duckdns.org/?a=commitdiff_plain;h=9d9c879413e8ea2bc805399c15f2e94b02f48e1d;p=DeDRM.git tools v6.2.0 Updated for B&N new scheme, added obok plugin, and many minor fixes, --- diff --git a/DeDRM_Macintosh_Application/DeDRM ReadMe.rtf b/DeDRM_Macintosh_Application/DeDRM ReadMe.rtf index 8813e94..cbc6d7c 100644 Binary files a/DeDRM_Macintosh_Application/DeDRM ReadMe.rtf and b/DeDRM_Macintosh_Application/DeDRM ReadMe.rtf differ diff --git a/DeDRM_Macintosh_Application/DeDRM.app.txt b/DeDRM_Macintosh_Application/DeDRM.app.txt index 0bfe842..d80e83a 100644 Binary files a/DeDRM_Macintosh_Application/DeDRM.app.txt and b/DeDRM_Macintosh_Application/DeDRM.app.txt differ diff --git a/DeDRM_Macintosh_Application/DeDRM.app/Contents/Info.plist b/DeDRM_Macintosh_Application/DeDRM.app/Contents/Info.plist index 86275f3..e251216 100644 --- a/DeDRM_Macintosh_Application/DeDRM.app/Contents/Info.plist +++ b/DeDRM_Macintosh_Application/DeDRM.app/Contents/Info.plist @@ -24,7 +24,7 @@ CFBundleExecutable droplet CFBundleGetInfoString - DeDRM AppleScript 6.1.0. Written 2010–2014 by Apprentice Alf and others. + DeDRM AppleScript 6.2.0. Written 2010–2015 by Apprentice Alf et al. CFBundleIconFile DeDRM CFBundleIdentifier @@ -36,25 +36,31 @@ CFBundlePackageType APPL CFBundleShortVersionString - 6.1.0 + 6.2.0 CFBundleSignature dplt LSRequiresCarbon + NSHumanReadableCopyright + Copyright © 2010–2015 Paul Durrant, Apprentice Alf and Apprentice Harper WindowState + bundleDividerCollapsed + + bundlePositionOfDivider + 728 dividerCollapsed - + eventLogLevel - -1 + 0 name ScriptWindowState positionOfDivider - 0.0 + 439 savedFrame - 85 100 1002 753 0 0 1440 878 - selectedTabView - event log + 77 69 1246 778 0 0 1440 877 + selectedTab + log diff --git a/DeDRM_Macintosh_Application/DeDRM.app/Contents/Resources/DeDRM_Barnes and Noble Key_Help.htm b/DeDRM_Macintosh_Application/DeDRM.app/Contents/Resources/DeDRM_Barnes and Noble Key_Help.htm index ac1b693..47da891 100644 --- a/DeDRM_Macintosh_Application/DeDRM.app/Contents/Resources/DeDRM_Barnes and Noble Key_Help.htm +++ b/DeDRM_Macintosh_Application/DeDRM.app/Contents/Resources/DeDRM_Barnes and Noble Key_Help.htm @@ -22,7 +22,24 @@ li {margin-top: 0.5em}

If you have upgraded from an earlier version of the plugin, any existing Barnes and Noble keys will have been automatically imported, so you might not need to do any more configuration. Continue reading for key generation and management instructions.

-

Creating New Keys:

+

Changes at Barnes & Noble

+ +

In mid-2014, Barnes & Noble changed the way they generated encryption keys. Instead of deriving the key from the user's name and credit card number, they started generating a random key themselves, sending that key through to devices when they connected to the Barnes & Noble servers. This means that some users will find that no combination of their name and CC# will work in decrypting their ebooks.

+ +

There is a work-around. Barnes & Noble’s desktop app NOOK Study generates a log file that contains the encryption key. You can download NOOK Study from https://yuzu.com/nsdownload.

+

Once downloaded, install the application, register with your Barnes & Noble or nook account, and download at least one DRMed ebook through NOOK Study. It will be saved somewhere in a folder called "My Barnes & Noble eBooks" in your Documents folder.

+

Now import that book into calibre. The log file and the key in the log should be automatically found by the plugin and used to decrypt the book.

+

If the automatic process doesn't work for you, you can still find extract it manually and save it as a .b64 file for import into the plugin's preferences as follows:

+
  1. In NOOK Study, select Settings/About (Windows) or NOOK Study/About NOOK Study (Mac) and in the dialog that appears click the link at the bottom to copy the log into the clipboard.
  2. +
  3. Paste the copied log into a text editor
  4. +
  5. Search for the text CCHashResponseV1
  6. +
  7. On the line below which starts with ccHash, copy the text between the " marks after ccHash, but don't include the " marks.
  8. +
  9. Save that text in a new plain text file, with file name extension .b64 (for example, key.b64)
  10. +
  11. Import that file into the preferences through this dialog, using the "Import Existing Key Files" button.
  12. +
+ + +

Old instructions: Creating New Keys:

On the right-hand side of the plugin’s customization dialog, you will see a button with an icon that looks like a green plus sign (+). Clicking this button will open a new dialog for entering the necessary data to generate a new key.