After yesterday’s fiasco, Coolstar is absolutely furious over the tweak developer who leaked the test IPA file. Although he can’t do much now, he will now implement a DRM mechanism to the upcoming build of Electra.
Why is Coolstar implementing a DRM in Electra?
For those who don’t know, Coolstar seeded the “test” copies of Electra RC1 (Cydia build) to select developers.
He also gave a strict directive to all testers that they ought to keep the IPA file private.
One of the testers went rogue and leaked the Electra RC1 IPA file publicly on the internet.
Here’s how Coolstar reacted to it on Twitter.
The young developer was sly enough to add a watermark to every IPA file he sent out. This allowed him to track down the rogue developer by inspecting the leaked file.
Now, users who are on the leaked RC1 will have trouble updating whereas users on beta versions will be good to go.
Is this decision right on Coolstar’s part?
This is, indeed, a poor decision on Coolstar’s part. He is purposely doing that just to stick it to all those who dared use the leaked IPA.
Punishing the end users who tried it doesn’t accomplish anything and only wastes the developer’s time.
This time would have been spent better had he actually invested it in support and releasing the final update.
The only way to prevent a leak online is to keep all your code or tool private until you really wish to release it.
Handing out files like candies to testers and developers without checking their credentials is just asking for trouble.
How can you bypass the DRM?
According to him, the DRM will detect all traces of the leaked IPA.
While I don’t know much about it, it definitely detects any bootstrap binaries present in the root bin folder.
Once it detects any leftover files, it blocks the user from running the tool.
If you unknowingly or purposely installed it, I will post a proper uninstallation tutorial very soon.
For more scene updates, give us a thumbs up on Twitter and Facebook.