Well your average dolt that jailbreaks and knows absolutely nothing about it would be blockaded. It's the folks that have hex editors and the time to figure it out that will find it easy. Which is still a little too much for many JB'ers. Besides, I want to see it broken so I can figure out how to stop it from happening in the next point release. That said... On my mac software I have a library I've written that makes cracking more difficult than using a hex editor and changing some bools. Specifically it uses a non MD5 hash to detect the slightest change in the binary, libraries or data files. Thus far, recompiling alone with absolutely no changes to the code will fail the hash check. Its been fairly successful. But I don't really understand code signing that well. so I am curious if such a hash would be possible on an iOS app. My understanding tells me that it would not work. The problem being of course that the hash is done after the app is built, archive builds preclude the inclusion of an after the fact data file.
On Nov 11, 2011, at 1:52 PM, Heijink, Hank wrote: >> The second is that I want to prevent my iOS apps from running on jailbroken >> devices. Doing this is easy, albeit easily circumvented too, however is it >> "Legal" to do this? > > If it's easily circumvented, why waste your time on it? If someone runs it on > a jailbroken device, they're already all about circumvention. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
