It came to light on Monday that the latest version of Adobe Digital Editions is sending metadata on ebooks that are read through the application to an Adobe server — in clear text.
I’ve personally verified the claim that this is happening, as have lots of other people. I particularly like Andromeda Yelton’s screencast, as it shows some of the steps that others can take to see this for themselves.
In particular, it looks like any ebook that has been opened in Digital Editions or added to a “library” there gets reported on. The original report by Nate Hofffelder at The Digital Reader also said that ebook that were not known to Digital Editions were being reported
, though I and others haven’t seen that — but at the moment, since nobody is saying that they’ve decompiled the program and analyzed exactly when Digital Editions sends its reports, it’s possible that Nate simply fell into a rare execution path. UPDATE 10 October 2014: Yesterday I was able to confirm that if an ereader device is attached to a PC and is recognized by ADE, metadata from the books on that device can also be sent in the clear.
This move by Adobe, whether or not they’re permanently storing the ebook reading history, and whether or not they think they have good intentions, is bad for a number of reasons:
- By sending the information in the clear, anybody can intercept it and choose to act on somebody’s choice of reading material. This applies to governments, corporations, and unenlightened but technically adept parents. And as far as state actors are concerned – it actually doesn’t matter that Digital Editions isn’t sending information like name and email addresses in the clear; the user’s IP address and the unique ID assigned by Digital Editions will often be sufficient for somebody to, with effort, link a reading history to an individual.
- The release notes from Adobe gave no hint that Digital Editions was going to start doing this. While Amazon’s Kindle platform also keeps track of reading history, at least Amazon has been relatively forthright about it.
- Digital Editions is part of the toolchain that a number of library ebook lending platforms use.
The last point is key. Everybody should be concerned about an app that spouts reading history in the clear, but librarians in particular have a professional responsibility to protect our user’s reading history.
What does it mean in the here and now? Some specific immediate steps I suggest for libraries is to:
- Publicize the problem to their patrons.
- Officially warn their patrons against using Digital Editions 4.0, and point to work arounds like pointing “adelogs.adobe.com” to “127.0.0.1” in hosts files.
- If they must use Digital Editions to borrow ebooks, to recommend the use of earlier versions, which do not appear to be spying on users.
However, there are things that also need to be done in the long term.
Accepting DRM has been a terrible dilemma for libraries – enabling and supporting, no matter how passively, tools for limiting access to information flies against our professional values. On the other hand, without some degree of acquiescence to it, libraries would be even more limited in their ability to offer current books to their patrons.
But as the Electronic Frontier Foundation points out, DRM as practiced today is fundamentally inimical to privacy. If, following Andromeda Yelton’s post this morning, we value our professional soul, something has to give.
In other words, we have to have a serious discussion about whether we can responsibly support any level of DRM in the ebooks that we offer to our patrons.
But there’s a more immediate step that we can take. This whole thing came to light because a “hacker acquaintance” of Nate’s decided to see what Digital Editions is sending home. And a key point? Once the testing starting, it probably didn’t take that hacker more than half an hour to see what was going on, and it may well have taken only five.
While the library profession probably doesn’t count very many professional security researchers among its ranks, this sort of testing is not black magic. Lots of systems librarians, sysadmins, and developers working for libraries already know how to use tcpdump and Wireshark and the like.
So what do we need to do? We need to stop blindly trusting our tools. We need to be suspicious, in other words, and put anything that we would recommend to our patrons to the test to verify that it is not leaking patron information.
This is where organizations like ALA can play an important role. Some things that ALA could do include:
- Establishing a clearinghouse for reports of security and privacy violations in library software.
- Distribute information on ways to perform security audits.
- Do testing of library software in house and hire security researches as needed.
- Provide institutional and legal support for these efforts.
That last point is key, and is why I’m calling on ALA in particular. There have been plenty of cases where software vendors have sued, or threatened to sue, folks who have pointed out security flaws. Rather than permitting that sort of chilling effect to be tolerated in the realm of library software, ALA can provide cover for individuals and libraries engaged in the testing that is necessary to protect our users.
Verifying our tools; a role for ALA? by Galen Charlton is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
3 thoughts on “Verifying our tools; a role for ALA?”
Comments are closed.