Copy protection

[Tilen]

Hi

can anyone point me to some good idea how to protect my software?

I would like to have this scenario:

1. Get Activation Key
2. On install enter Activation Key and connect to internet
3. Connect to server to validate that Activation Key has not been used, yet
4. IF OK -> Set Registry's value as something to say 'valid/OK/activated...'

This seems like a good scenario, because they need Activation Key from me, and each Key can only be used once.

And there is no need for verification of any kind, at each start-ups of software. Which is good.

No, how would I go about protecting this installation againt copying it on another machine?

Just by copying installation folder and registry keys, would work. If I write to .ini file, is even easier.

Any suggestions?

Thanx, tilen

 

[melmitts]

You might check out the demos and tutorials at

http://www.exeshield.com/

The customer sends you a code, then you provide either a serial number or license file for your program on the computer where it was installed.

Let me give you a quick personal experience. I found a quick and easy backup program and paid 60.00 for it. Its protection was to "phone home" to register. Then at random intervals it would "phone home" to verify the registration. However, every time their registration server would hiccup, my registration crashed and I had to call, wait on hold and beg them to reset their server.

That software was deleted long ago...

Bottom line, don't annoy your potential customers too much. There will always be someone who figures out how defeat your system no matter what you do. That is just life.

Good Luck on your project.

Mel

 

[Tilen]

Thanx.

I will only use internet connection for first run after installation. I will also use it to check when software checks for updates. So, no annoying checking after installation.

And when it checks for updates it will also check serial numbers and if it's something wrong will disable software.

And for copy-protection I will use some system info to make sure serial number is for the same machine. If not, it won't work.

The serial number used once will be disabled for new installations. So, only one installation per serial.

On Uninstall it will connect to the internet again and mark serial to be available again.

If there's no internet connection, it will be available via email.

I guess this is good plan and it will give me more control over intallations.

If anyone has any comments on this, please advise.

thanx

 

[Griffyn]

I would also provide a 7 day window (or more) from the first time the software is run. If your server is unavailable to register the new software, then you should allow it to continue running during this 7 period.

It's important to focus on the end user's experience with your software. Anything you set up that will require them to do something for you is a bad thing, so be sure to make it as painless as possible.

I agree with Mel - if your software is popular enough, it will be cracked. There's no getting around this.

 

[Tilen]

Thanx, a 7 day window is a good suggestion.

I know there's no perfect protection. And if it's cracked -> popular -> good money anyway!