So, we have two issues, neither of them useful to end users. On Adobe's end, we have a protection scheme that requires an internet connection. That's classic DRM -- phone home, get permission… all well and good (NOT REALLY) until someone needs access to do ents but can't because they're not connected to the internet.


Then we have an update that breaks the connection Adobe's DRM relies on, forcing the same problem on users who do have internet access. The problem with DRM schemes like these is that they rely on a bunch of parts that aren't interconnected (Adobe, Windows) but both have to be working properly to get the job done... rather than just, say, open Adobe Reader and be done with it. Subtract an internet connection and Adobe's do ents are useless, even to authorized users. Throw a suprisingly volatile Windows update into the mix and end users doing everything right are still screwed. Combine the two and sensitive do ents are suddenly so "protected" that a majority of users can't even view them. And, remember, this is a "privilege" corporate customers pay for.


DRM: still mostly useless and still mainly a pain in the ass for paying customers.
https://www.techdirt.com/articles/20...ers-most.shtml