My program has been cracked - PLEASE READ

[filburt1]

My program has been cracked (http://www.liquid2k.net/filburt1/passprog is my program). Someone created a valid username/regcode for the registration. What can I do? All I have is the ZIP file containing the crack, and the cracker's name.

YOU CAN'T BELIEVE HOW PISSED I AM. FOR THE LOVE OF GOD, HELP!

[Bloodeye]

Looks like it's time to change your registration scheme, and update your program so that if users download it they won't be able to use the crack on it.

Bummer...

On a seperate note....where did you find the crack at?
.....Just kidding.....

You might be able to close down the site that the crack is being offered on. Do a lookup on the site, get the number and make a call. Wouldn't hurt to try...

[JungleMan]

Filiburt:

You must accept the fact that with time a program WILL be cracked. there is no way to avoid it. Even the best of encryption schemes have been cracked.

the majority of people don't know about these though..

[parksie]

Superior encryption schemes are resistant to cracking - as in, even if it is cracked it makes no difference - all you know is HOW to decrypt without the password/phrase, which won't help when to do so will take longer than the age of the universe

[filburt1]

*first, bump*

I had an idea. How about when the user enters the registration code it is first compared against a list of already used regkeys online. If the key already exists, then the registration is rejected.

[filburt1]

*another bump TO GET A REPLY! *

[Bloodeye]

Pro's - It allows you to keep the same registration scheme, and blacklist the public regkeys from working. You could build this into your program or have it check online.

Con's - The same cracked registration scheme is being used. All crackers need to do is pump out some more regkeys. The good crackers will even make a keymaker. If that happens then you will need to come up with a different registration scheme.

The best thing to do is make a reg. scheme that can be easily altered by you in your code. So when a crack is developed for your reg. scheme, all you need to do is make a slight adjustment to your code. Then compile the new and improved version, and offer that to the public. Then the crack won't work for that version. Of course if they cracked it once they can crack it again.

If you go this route you'll soon find yourself in a never ending circle trying to keep ahead of the crackers. I hate to say it, but it's a no win situation especially if you have a popular program. The more popular it is, the more cracks there are for it. This is one of the reasons you see alot of programs going the "advertisement" route. Developers offer there program for free, and make money from their workproduct through "Ads".

Just my 2¢ worth.....

[filburt1]

Damn, this sucks.

I was trying to take the *XP approach for this (Activation) but that just doesn't work.

And my program isn't that popular. Maybe I'll make it postcardware or something.