Stop Patching/Cracking

[Lee Stevens]

Hey,

I'm useing a auth system for my programme and wanted to no how people Patch/Crack programmes and anything to help stop it?

Thanks

[Pino]

It depends on how your AUTH program runs, each program will be cracked in a differnet way depending on how the program i set up.

Pino

[Lee Stevens]

Mine uses Mac Code, but I understand they can be changed, also uses a server to get contract type, but that can also be changed by a programme?

[Pino]

Ok the thing is any programe you produce is crackable. Given enough time and motivation, you need to work out if you think people are going to crack it, and if so do your best to make it take them as long as possible (Which it sounds like you have done)

Pino

[TheUsed]

When programming I would suggest using the dotfuscator. which I believe is to stop the program from being disassembled. That way no one can browse your code and use a hex editor to alter your program. Now if you want no one at all to crack your program it will be very difficult.

I have the following suggestions:

1. Add values to the registry for registration (this can be cracked if the user is smart and uses a program to monitor the registry)

2. Use a web service and control registration remotely.

3. Make a registration code based off of the computer name

4. Make a registration code based off of multiple hardware configurations

5. have your program compare the .exe to a remote .exe and lock it out if it comes back false.

[keystone_paul]

5. have your program compare the .exe to a remote .exe and lock it out if it comes back false.

The problem with that is - presumably you want to do this to check if someone has altered the code from the original code? If they have, then there's every chance they will alter your code that checks to see if the code has been altered.

Its a bit catch 22.

[TheUsed]

is there any possible way to program your program to recompile itself if there is anyway to check for changes. or to lock certain sections of your exe file?