Software Piracy

Hello, gurus,

Had a general question and just looking for some guidance. I'm developing some software using VB.NET 2003. After it's packaged and everything, I would like to sell it to others. Can someone give me some pointers and/or point me in the direction (books, websites, etc.) of how I can prevent software piracy? I know no method is full proof (otherwise ppl couldn't break into windows! lol) but I'd like to be able to do stuff like:

require a key supplied with software to use
registering software
make it so software knows if its trying to be installed on a second pc

Any suggestions/ideas/guidance?

Thanks in advance!

Strick

The best way would be to not deploy your software.

This is the best way the do it anyways, publish each copy so that it has a unique signature or ID. Require activation online so that the signture or ID is logged, along with a system hardware hash. Block all activations that have a logged signature/ID and a different hash code.

Allow activation for signatures for up to two hashes since they might upgrade. Perform online checks every two months and block the second hash if both are in use.

It isn't fool proof, but unless it's some major wicked app, no one would bother to crack it (by patching the signature or ID).

Welll I guess you could think of piracy in two forms. One, the duplication of your software for installation on multiple machines. And two, Hacking or Cracking of your code or registration logic.

Using a deccent Obfusicator is good as it will keep most hackers away but the determined "professional" types will still get it, just takes more work and knowledge. The registration logic is good but you need to put in place a system theat will allow for the resetting of the instalation or registration due to hardware upgrades and reformats. One way is to get the physical hard drive servial number and not the hd volume serial number that changes each time you format. Confirmation or validation via email should be good to unlock the install dfepending on your critieria.

There are legit cases in which users may change hardware configurations or quite possibly decomission the entire system and attempt to install on another system. these types of registrations would prevent users from using their product even though they paid for it.

I suspect the main concern could quite possibly be the excessive reproduction and distrobution of the said application with out consent.

perhaps that's where some focus should be cast.