Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
Protecting executable from reverse engineering?
As primary goal, I would like to encrypt information about used header files and libraries
For the most part my application is writen in C++, using only standard I/O methods from the iOS SDK
The app store already encrypts your application’s executable file (or most of it) before sending it to a user’s device. The iOS kernel decrypts the encrypted part of the file, in memory, when it launches your app.
Since Objective-C looks up classes by name when loading dynamic libraries (like UIKit and Foundation), and looks up method selectors by name at runtime, those class and selector strings must appear in your executable, but they are in the encrypted part of the file.
Jailbreakers can already defeat the iOS encryption system by examining your app’s memory after the kernel has decrypted it.
Spending more time trying to hide these strings is almost certainly a waste of time.
UPDATE
If your target market is in a part of the world where jailbreaking is common, you might want to look for an application idea that uses a server back-end, and use in-app purchase to sell server access as a consumable item. Your server can verify that users have paid for server access, and you can ban accounts that try to steal access.