Showing posts with label acs5. Show all posts
Showing posts with label acs5. Show all posts

Tuesday, October 07, 2014

Are Adobe Secretly Watching You Read Via DRM?



The question of privacy on the internet has once again raised its head with the posting by Digital Reader on Adobe’s ACS DRM system and what is claimed to be excessive data gathering of personal information from consumer’s elibraries.

We can’t comment on whether the facts as presented are true or false, but we are able to say that if true, they are a significant shift from where Adobe started from and seriously question the role of DRM and whether consumer privacy rights have been breeched.

Abobe DRM history goes back many years. ACS3 was widely used by retailers but effectively broken and open. The start of the latest ebook revolution was initiated with the introduction of the eInk readers and when Sony entered the fray they wanted a DRM system which would effectively give them a march on the rest. Adobe also wanted to regain control of a space they had clearly lost. Overdrive had also built a ACS4 beta that they were using to control their market. We remember Adobe’s introduction of ACS4 and their lack of market awareness and often rigid mind-set and coupled with Sony’s desire to rule the world, we had many often fraught conversations with the two of them but the rest of the market wasn’t ready and so they won the initial battle. Years later it’s a different story and many have either migrated to their own DRM. Amazon and Apple never did join and Kobo and Nook grew alternative offers and Overdrive stuck with their own variant.

Adobe then went into what can best described as the Dark Ages where they still championed interoperability, but where leaderless and gave up trying to manage micropayments and gave this up to a small handful of agents who managed the retail facing activity and collected the money. They then came up with ACS5 or a tighter model which was part born out of the fact that ACS4 could easily be broken by anyone who asked the right questions on the Internet and part by the fact that they were clearly being squeezed out by the big channels. Unfortunately ACS5 has some basic issues which forced Adobe to retract their initially statements and backtrack on their timelines to force full migration to the new platform.

So today we have the news that Abode appear to be data gathering consumer usage information at title level and also at library level. What was read when, what wasn’t read, and probably much more? Is this right or wrong?

Well Adobe provide a DRM locking service aimed at validating ownership and stamping this such that they can ensure rights are managed with respect to devices, etc. Why on earth do they want to gather data on usage other than to sell back to publishers, retailers and libraries. Did they offer and opt in, or opt out to consumers is a mute question and we would suggest that they had to in order to snoop.

They apparently doing this not through the standard interface with hosting sites but through a mole application in Digital Editions that they plant into the consumer library or device. We would like to see the snooper application flagged as unauthorised by the security systems and users being given at least the choice of allowing it in. Whether the Adobe service will work without the mole is an interesting question.

We have to accept that Amazon, Apple, Nook, Kobo and Overdrive all can gather information on their consumers and their walled gardens allow this, but they are walled gardens. Adobe promotes itself as open and interoperable and importantly does not have consumer customer relationships to build in the same way. Again it begs the question what do they intend to do with this information and is it being resold and if so to whom?

However, all this a new news and we await more information about Abode’s intent and what is behind the intrusion into consumer’s private libraries and reading habits.

Personally, if the facts bear up to what has been reported, then Adobe has single handily done more harm to DRM than all the articles every written about it. Consumers if made aware of it will probably shun and question the violation of their privacy.


Finally, we hope that the wider media picks this story up and fully investigates it and if collaborated exposes it to the consumer.  

6th Oct 2014

Wednesday, February 05, 2014

Adobe Climb Down Over ACS5 Deadline


After the storms comes the calm and time to reflect.
Adobe have now climbed down from their ACS5 stance and have left the migration timetable in the hands of their customers. A statement posted on the Datalogics blog says:
As stated during our January 29th Datalogics and Adobe webinar announcing the release of the new hardened Digital Rights Management (DRM) for Reader Mobile SDK (RMSDK) 10 and Adobe Content Server (ACS) 5, Adobe revealed a July 2014 time table for migrating to RMSDK 10 and ACS 5.
After receiving feedback from customers and webinar attendees, Adobe has revised the migration timetable for customers.  “Adobe does not plan to stop support for ACS 4 or RMSDK 9.  ACS 5 books will be delivered to the older RMSDK 9 based readers”, according to Shameer Ayyappan, Senior Product Manager at Adobe.  “We will let our resellers and publishers decide when they wish to set the DRM flag on ACS 5, thus enforcing the need for RMSDK 10 based readers.”
In other words, ACS and RMSDK customers can migrate to the new hardened DRM that provides a higher degree of security to EPUB & PDF content and prevents unauthorized viewing of content now and in the future in a timeframe that makes sense for them.
As stated during our January 29th Datalogics and Adobe webinar announcing the release of the new hardened Digital Rights Management (DRM) for Reader Mobile SDK (RMSDK) 10 and Adobe Content Server (ACS) 5, Adobe revealed a July 2014 time table for migrating to RMSDK 10 and ACS 5.
After receiving feedback from customers and webinar attendees, Adobe has revised the migration timetable for customers.  “Adobe does not plan to stop support for ACS 4 or RMSDK 9.  ACS 5 books will be delivered to the older RMSDK 9 based readers”, according to Shameer Ayyappan, Senior Product Manager at Adobe.  “We will let our resellers and publishers decide when they wish to set the DRM flag on ACS 5, thus enforcing the need for RMSDK 10 based readers.”
In other words, ACS and RMSDK customers can migrate to the new hardened DRM that provides a higher degree of security to EPUB & PDF content and prevents unauthorized viewing of content now and in the future in a timeframe that makes sense for them.
We welcome the change of softening of the Adobe position but now question what really drove them to do it in the first place?

Does the ebook world really need a hardened DRM that will be broken before it’s widely adopted? Does this PR slip give us all a wake up call to seriously question the benefits of hard DRM, its costs and the fact that it actually can restrict business and as demonstrated by this PR slip put many’s business in the hands of someone who merely operates a toll booth and adds cost. 

Monday, February 03, 2014

Adobe to 'Harden' their Broken DRM



Last week we asked questions about the state of Adobe’s widely adopted ACS4 DRM service and the implications of their announced migration to ACS5. Then we knew little of their plans and only of their intent, but today more has come to light on how they plan to achieve the move and the potential implications for those who sell the service and the consumer who has the files.

Below is Youtube link to a webinar that Datalogics did alongside Adobe last week. It is not recommended that you watch it all as it is not user friendly and aimed at technicians. However some of the salient points can be obtained by cutting to this shortened clip http://www.youtube.com/watch?v=9qb-sXVlK_o&t=24m48s . Adobe confirms that it will ‘harden’ their DRM in July and force migration and that this will effectively kill compatibility with older RMSDK9 (reader) based apps and devices. The move is understandable from Adobe’s perspective and very reminiscent to the language that came out in 2006 when the introduced ACS4 to strict deadlines.

What Adobe have failed to grasp is that many devices (readers) that have supported ACS4 will have significant software and maybe firmware upgrades to achieve in what is a relatively short period and inevitably there will be disconnects. It is not possible to comment on the myriad of old eink readers out there but…

Many pundits have taken aim at Amazon, Apple, Kobo, Nook and their proprietary DRM systems. However, all of these effectively can control their own environment and evolve seamlessly. Adobe’s DRM may be usable by others, but as demonstrated by this announcement, it puts your business and commercial transactions charges in Adobe’s hands. Short term this may be fine, but long term is it wise.com?
The Adobe use of the term ‘hardened DRM’ is quite apt and we have to question whether we are being taken done a road which is technology applied for technology sake? ACS4 was easily hacked and broken so one option is to ‘harden’ it and make it more difficult to hack. The other is to migrate away from encryption and find ways to make business easier for all and grow the market.

DRM is not about encrypted hard DRM. It is about digital rights management, be it hard, soft or none and we have to ask what we are trying to achieve and what works best for the market? Adobe by moving part of the individual licence that was previously on the rendering server back to the issuing server and in doing so have tightened their grip on the file, but they have increased the cost of doing business and offered little in return. Adobe is increasingly creating its own walled garden and it begs the question – is it all necessary, or is it a simple case of the Emperor having no clothes and nobody strong enough to say so?

This migration to ACS5 in fact could do more damage to the reputation of DRM that all the stones thrown at Amazon’s system.

We were around pre ACS4 and were involved in the initial services. We also sat down with others trying to seek an alternative option to ACS4 but had little time and much pressure to roll over. Trying to change Adobe’s corporate mind-set is all but impossible. Today there are many alternative options and cloud based services all but render the existing ebook model redundant. As we move towards subscription based online and ‘as much as you can eat services’, many now seek a way to escape the Adobe locked in transaction charges.

However, as we have suggested before we should not rush headlong into no DRM as that could be equally as short sighted. We must look at softer watermarking DRM which can be individually hacked, but if tied to a central licencing registry would provide provenance of legitimate ownership, which in turn could enable that often feared resell market some creditability.


It is also interesting to note the only now some 8 years after ACS4 came to market are some of the business models and issues, which were raised at the beginning are starting to be addressed. Shared devices, bulk downloads, subscriptions, educational loans etc where raised at the time but not seen by Adobe and Overdrive as important then. It drives home the point that hard DRM may not just lock up the files but may also lock up the business from doing business their way. 

Thursday, January 23, 2014

Adobe Accept ACS4 Broken?

Adobe have long been associated with publishing and the development tools associated with the development of content and although they have successfully seen off the likes of Quark and established InDesign as the tool of choice to many, they have long floundered in the area of DRM.

Today we read of their latest step change to introduce ACS5, which is aimed at tightening the security and replacing the easily broken and much maligned ACS4. There is a question as to whether it will be widely adopted and also of whether how quickly it will be broken by those who wish to break it. There is also the question that if they accept that they are doing it to primarily address ACS4, what of the ACS4 licences being issues and charged for in the market today?

Some 8 years ago they dropped the then much broken ACS3 offer and with the backing of Sony and Overdrive delivered ACS4. The objective was to establish a cross platform ‘open’ service that could be used by all, on any device and at a small transaction licence fee to Adobe, which was centrally controlled with real time licence authentication. The problems started early. Much of the original specification was done with the help of a single party who mainly operated in a single market and whose input made it unfriendly and cumbersome in other sectors. The original restrictions on devices and the interface with Digital Editions was restrictive and confusing to users and although these have been greatly relaxed the basic process and controls remain. Eight years on it remains cumbersome and unfriendly.

A few years later they found that they were not geared to dealing with small accounts and collecting micropayments. So they outsourced this activity to a couple of partners who were more incentivised to dealing with customers. Prior to this move and after the departure of the main driver and movement of his successor within Adobe, it was almost impossible to find the person in Adobe who could make any commercial decisions or even knew much about it.

ACS4 had other problems. The model was based on a server licence plus transaction fee on each purchase download of some 25 cents and a reduced fee of 8 cents for each library loan up to 60 days. As the demand grew for ebooks and the prices dropped the transaction cost often became a thorn in the side of many. It is in effect a fixed sales tax that is imposed irrespective of the cost of the sale and is not include in the publication price. Today Amazon and Apple each have their own DRM which obviously are incompatible and others such as Kobo and Nook have understandably quietly started to go their own way. Sony remains an also ran and probably still has two DRM solutions one of which is ACS4. More importantly some 85% of all sales in all markets are driven by proprietorial DRM solutions and although ACS4 is still seen by some as ‘open’, to many ACS4 is in reality the same. However ACS4 is only one DRM service that directly charges the retailer and lives off their sales.

Perhaps Adobe should have adopted a more long term and integrated approach by embedding both encrypted and later watermarked solutions within InDesign and collected the money in the upstream development. They could have still offered the downstream licence operation but would have probably achieved greater control of the market. Files could have been automatically exported in multiple formats all offering the publisher multiple channels and retailers an incentive to do what they do best – price and sell. Also it should be noted that as Adobe move towards the subscription based licencing of all their tools, this simpler approach could have been bundled in as a value added incentive to publishers.

We have seen the emergence of streamed cloud based ebook services. Whether these are app or browser driven they do not need ACS4 or 5 and can effectively be far more secure in their offer and more transparent in how they achieve it. Maybe ACSx was built for a downloaded file world that may not be so relevant in the near future.


There remains questions about the cost of ACS5 migration and its associated family of change. There remain questions on how Adobe are going to stimulate the transition and whether, like in the ACS3 to 4 move, they will effectively force it to happen even though their hand is considerably weaker this time round. There remains questions on the backward compatibility of ACS5 and ACS4 licences. However, to many today there is still a bigger question over encrypted DRM and whether we should not migrate to a watermarking soft DRM with authentication of ownership , or be factored into an epub format and service, or whether we should just go no DRM?