objective c - Being a cracker nightmare! -

I'm trying to make a code difficult to use Objective-C on a Mac.

One thing I have to do is to see if the application was broken.

I'm new to Objective-C and Xcode and the way I imagine testing my application, I always end up in a basic test that can easily be patched . For example: In a certain part of the binary, I am about to test for the existence of a given value. This operation will be something like this:

"Is this value = x?" If not, it breaks.

It is very easy to crack.

I am trying to visualize some of the things which can do some testing, do not appear in the form of a test which can easily be patched.

I know that I can not stop the 100% theft, but at least I am trying to make things even more difficult because most of the crackers get out of there.

Thanks for any help.

To make them hard to evaluate your plan and change your plan regularly. A textbook example is that they check at the odd time that it takes time for them to find all cross references during the progress of the evaluation of sources of your check and license. Combine with multiple checks and you should be set for most releases, just add a good dose of creativity when planning your plan. Apart from this, their game has little fun; To release the crack that fails in the first month after the release of the crack, to fix them ... well, it can only be confused with you, but if you are trying to fight them in the first place ...

> This is an interesting community; If you are new to it, study of communities will also be beneficial. As mentioned earlier, cracks are for the challenge, some product versions will simplify their copy protection plan for 'free advertising'. So ... you can not really fight hard to break because if someone is determined, it will only waste their time and will disappoint you. Considering the culture can be interesting, you are probably in the best position, if you accept that the breakage is equivalent to 'popular software' and therefore, you should be happy. You generally do not want to sleep over it (although there are definitely exceptions) Also, since this question is listed in the MAC category: I am not going to digest the statistics, but if you are targeting OS X So your software is less likely to pay attention to firecrackers.

Again beginner programmer, clever use of that information (and acceptance) you all must know to fight effectively with crackers.