Quote:
Originally Posted by Leseratte_10
Given that you can call Adobe to have that limit reset, and given that you could also just make a new dummy AdobeID if you're using DeDRM, I don't think it's worth all the effort. The only issue / potential problem with this method (dummy ADE ID) would be if you're buying books from publishers that enforce the new, uncracked DRM, then the books would be stuck on the dummy account.
|
Another reason for cloning an existing ADE activation is that it would provide a means to verify that the interaction between the plugin and Adept servers matches that of an actual ADE installation using the same credentials and keys by comparing packet captures. That could be used to catch any remaining discrepancies between ADE and the plugin, making it less likely that use of the plugin could be detected by Adobe. Of course that would only work if the activation being cloned came from an ADE version that the plugin is able to emulate.
I do agree it would be a fair amount of additional work for little potential benefit.
----------------
Thinking about this raises the question of what ADE version does the plugin emulate?
I have ADE for Windows version 2.0.1 installed on my PC running Windows 11 and it identifies itself as clientVersion 2.0.1.78765, softwareVersion 9.3.58046, and clientOS of "Windows Vista". (Looking at the code it has a fixed set of possible Windows versions that it can report with Vista being the newest possible.)
I also have an installer file for ADE version 3.0. It will apparently will identify itself as clientVersion 3.0.1, softwareVersion 10.0.85385, and clientOS going up to "Windows 8.1".
The plugin appears to identify itself to Adobe as clientVersion "Desktop" with softwareVersion 10.0.4, and clientOS of "Windows 10". I am curious to know what ADE version this is intended to correspond to.