New Marketplace Advanced Copy Protection now also cracked
2 min. read
Published on
Share this article
Improve this guide
Read our disclosure page to find out how can you help MSPoweruser sustain the editorial team Read more
As we predicted, Microsoft’s anti-piracy measures for the Windows Mobile Marketplace, even on its second level (the first one was delete the cab file) did last very long at all.
Chainfire wrote on XDA-Developers:
I have now cracked the "advanced" copy protection used by Marketplace. As you may know, this is a "better" protection than the original "CAB copy protection" Marketplace offered. This "advanced" protection uses license keys that are verified when you run the application, and given out and controlled by Microsoft.
Several developers are annoyed that Microsoft does not allow us to use our own licensing schemes, and are forced to use "no protection" (the original CAB copy protection) or use Microsoft’s scheme which is essentially a single point of failure for all Marketplace protected apps.
This new "advanced" protection was released today by Microsoft, and as far as I know no app available already uses it at the time of this writing.
So I got the code snippets you are supposed to put in your app and it was simply jawdroppingly WTF. While it was not exactly easy to beat, it took me less than two hours to devise a "generic" hack, without modifying any files on the device. (Well hey, at least it’s better than the 5 minutes it took for the "basic" protection, right?)
A "generic" hack? Yes, by this I mean that this single hack (actually, running an EXE in the background) will completely bypass the entire code snippet provided by Microsoft that is supposed to check and validate your license code, for all Marketplace apps that use this "advanced" protection.
Chainfire will not be releasing the hack, which involves patching the cryptographic module while it is running in the background. His goal is to get Microsoft to realize a mono-culture of copy protection means no protection at all for all, and for Microsoft to allow developers to use their own various modules. While we ourselves do not think this is an ideal solution, the ease with which their new protection has been bypassed remains frightening to developers, and may cause them to stay away from the embryonic Windows Mobile Marketplace.
