Quote:
Originally Posted by Kalimba
Exactly. There are a nearly infinite number of ways to camouflage the creation of the @"SignerIdentity" string. Store it reversed (@"ytitnedIrengiS"), store it character by character and assemble the string with multiple methods, apply a bit manipulation (e.g. XOR with 0xFF) to each character in the string, etc.
|
Or what you could do, to make it impossible or painful to find out where the checking code is....
#define INIT_STRING @"SignerIdentity"
And then when you create a new string anywhere (should be a lot in your average program), even though its overhead, always assign it your #define.
NSString *aString = INIT_STRING; ///do this for all of your temp strings
Then also use the above method of functional creation of the real string.
I'm sure the average hacker will give up placing the command in your code trying to find the right place to overlook your check for a jail broken app.
mis-information at its best.
