Adobe Digital Editions

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Adobe Digital Editions
A screenshot of Adobe Digital Editions in library view
Adobe Digital Editions - Library View
Developer(s) Adobe Systems
Stable release 4.5.1 / March 8, 2016; 8 years ago (2016-03-08)
Operating system Mac OS X, Microsoft Windows, iOS, Android
Type E-Books reading and library management
License Proprietary
Website Adobe Digital Editions Homepage

Adobe Digital Editions (abbreviated ADE) is an ebook reader software program from Adobe Systems, built initially (1.x version) using Adobe Flash. It is used for acquiring, managing, and reading eBooks, digital newspapers, and other digital publications. The software supports PDF, XHTML (through the nonproprietary EPUB file type specification) and Flash-based content. It implements a proprietary scheme of Digital Rights Management ("DRM") which, since the version 1.5 release in May 2008, allows document sharing among multiple devices and user authentication via an Adobe ID. ADE is a successor to Adobe eBook Reader.[1]

Windows and OS X versions of Adobe Digital Editions were released on June 19, 2007. Previous versions of the software required version 9.0 of Adobe Flash Player. Starting with version 2.0, however, which relies on .Net 3.5 on Windows, Flash Player is no longer supported. Adobe initiated development of a Linux version of ADE in 2007; however, this has not had any beta release or any formal updates.[2]

Digital rights management

Adobe Digital Editions uses the proprietary ADEPT (Adobe Digital Experience Protection Technology) Digital Rights Management scheme,[3] which is also implemented on some e-book readers, including iPads and many Android devices, but not Kindles.[4] The software locks content to up to six machines and allows the user to view the content on each of them. Barnes & Noble (B&N) ebooks are protected with a variant of ADEPT.[citation needed]

In March 2009, the author of the reverse engineering blog i♥cabbages announced that they had broken the scheme.[5]

When viewing an ebook, Adobe Digital Editions by default stores the ebook locally as PDF files on Windows machines. These files can be copied and handled like other files, but they cannot be opened except with Adobe Digital Editions. Adobe's website has virtually no information on Adept except on its trademark page and a statement that OverDrive is compatible.[6]

Data collection concern

On 6 October 2014, Nate Hoffelder reported in The Digital Reader that Adobe Digital Editions version 4 ("ADE4") was sending extensive information about ebooks back to Adobe, including ebooks read by a user as well as ebooks stored on the same machine but not opened in ADE4.[7] This was confirmed by Sean Gallagher writing in Ars Technica[8] and by others.[9] However, no one else has confirmed the report that books never opened in ADE nor in the ADE library are logged.[8] Hoffelder reported that the information collected included "[which] ebooks that have been opened, which pages were read, and in what order... including the title, publisher, and other metadata for the book".[7] He also reported that all this data was sent in clear text—that is, not protected by any form of encryption.[7] This would make it easy for a third party to read this information. This data was collected for borrowed library books and for books NOT protected by any form of DRM. Hoffelder suggested that such a practice might violate various privacy laws. The Electronic Frontier Foundation (EFF) made a similar suggestion.[10]

Adobe responded that their practice was justified by their license agreement and denied collecting data on any book not currently opened for reading. Specifically, their statement said:

"All information collected from the user is collected solely for purposes such as license validation and to facilitate the implementation of different licensing models by publishers. Additionally, this information is solely collected for the eBook currently being read by the user and not for any other eBook in the user’s library or read/available in any other reader. User privacy is very important to Adobe, and all data collection in Adobe Digital Editions is in line with the end user license agreement and the Adobe Privacy Policy."[11][12][13]

Gary Price, writing in INFOdocket (an online publication sponsored by Library Journal), views the matter as of serious concern, but sees it as another instance of concerns present but largely unaddressed for years.[13] The article also posts Adobe's response to the issue.

Corynne McSherry, of the EFF, wrote that "sending this information in plain text undermines decades of efforts by libraries and bookstores to protect the privacy of their patrons and customers."[10] McSherry further speculated that this incident, if it generated enough complaints and outrage, might reduce or eliminate the prevalence of DRM for ebooks, as the Sony rootkit scandal did for music.[10]

On 7 October 2014, Lisa Tolliver, writing in Lisa Tolliver On Air and Online, likened "ADE 4-Gate" to documented data collection efforts by schools that use electronic versions of textbooks to spy on students as they read them"[14][15] and to large players in the ebook market besides Adobe (e.g., Amazon,[16] Barnes & Noble, CourseSmart,[15] Kobo, and Sony[17][18]) as well as other media industry segments [e.g., LG smart televisions (which in at least one case was discovered to have uploaded data from a user's USB-connected device[19][20]), Microsoft Kinect (which counts the number of people in the room to make sure not too many are using it[21]), Netflix (whose "use of viewer's data is applauded as a key success factor"[22]), and RealNetworks (which was successfully sued in the late 1990s for violating various privacy and fraud laws by surreptitiously recording data, including music preferences, from millions of Internet users[23])]. Her piece, titled "Digital Readers: Beware! Adobe Digital Editions 4 Spies On Users (And They're Not the Only Ones)", includes a short, tongue-in-cheek horror story, prefaced by the statements: "Think of the children! I did", and titled: "Who's Reading Whom? (Be Afraid. Be Very Afraid.)".[24]

In October 2014, Adobe released version 4.0.1 of the software, which sends data to Adobe in a secure transmission (using HTTPS).[25]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 10.2 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. What We Can Learn From The Adobe E-Reader Mess

External links