Quote:
Originally Posted by Iphone Rocks
I read all the different ways posted in this thread, and the encryption check seemed the best and safest way to go. I've implemented it and I'm in the same situation as above. However I compile my app, I get a crypt_cmd->cryptid equal 0, for all (non-simulator) targets and all configurations.
The assumption though is that binary encryption won't actually occur until Apple signs the binary.
I used the otool -l command to check binaries I previously submitted to Apple and the cryptid is 0. I use it on all apps I downloaded from the App Store, including my apps, and the cryptid is 1.
So I'm not worried about this, binary encryption will occur when Apple signs it and puts it in the store.
But, my concern is this: When the reviewer puts it on their device to test it, is the binary already signed by Apple and therefore encrypted? Cause if it isn't, then the app will think the reviewer is running a pirated copy right?
|
I honestly don't know the answer to that question. I've implemented this check in my code and my app got into the App Store just fine. Either Apple is not thoroughly checking the apps, or they encrypt the app before running it. I'll test this out in my next update, I'll run this check on one of my free apps, and if it returns negative I'll show an alert asking if this person is a tester. What do you think?
Quote:
Originally Posted by iPhoneAppStudio
I think that you are probably correct. I am concerned about what the reviewer might see too. It seems unlikely that Apple would sign the binary before it has been reviewed.
I have an app that was recently featured on the "What's Hot" list. It only had the obscured signer identity check for piracy and was cracked almost immediately. So far piracy doesn't look outrageous but I have had other apps where the piracy was as high as 80%. I've incorporated all of the other countermeasures but I'd like to add encryption before I release the next version.
I was also considering giving Oliver's (Dr Touch) AntiPiracy a try. Honestly, I would rather spend my time developing cool stuff for my apps than trying to thwart the crackers. But of course his code is a bigger target than a home brewed solution.
|
I agree with you, developers shouldn't have to develop Anti-Piracy code for the iPhone, we should be spending time making cool features for our apps.
I've never used Dr Touch's AntiPiracy code, but just by watching the commercial it seems that he uses the encryption method, and probably a couple more listed in this tutorial. Feel free to try it and tell us how it is though.
