i have got software developed in VC++ / Win32 API based , if i have to secure the my software , so that client can installed the software only on one machine how do i go about it .
That one is a tough nut to crack. I guess the standard answer would be to write machine-specific information to the installation media during app setup to mark the media as "used" (the GUID - Globally Unique Identifier might be a good candidate). This wouldn't work with read-only media, i.e. CD-ROM.
...and it doesn't address the problem of copying the media prior to using it for setup. There are a number of ways to circumvent this but none of them are easy or 100% reliable. You could, for instance, play with a disk's physical sectors or encrypt the FAT on a rewritable portion of the media to make it hard-to-copy. I have tried these schemes (and others) They work quite well in most situations but they are only practical when the software is distributed as a physical package.
Copy protection used to be very common but it has fallen by the way-side and today you may find it in only the most expensive software products. Most of them ship with a hardware lock (a nasty little tangle of circuits potted into a solid block and attached by way of a communications port or inserted in a slot). Trying to prevent pirates from distributing your software may not be worth the effort. You might be able to inhibit the theft by trying one of the examples I cited or by using the current popular scheme: make your product available for download on the internet but make sure it won't install or run without a "key" or password. The customer receives the key after he makes payment. (Anybody who has taken a look at the warez sites and seen the thousands of product keys available on the Internet should realize that this is poor way to copy protect software but, at least, it helps to keep honest people honest.)
Let your software ask for a key on first use. Use the following steps:
1. show a number to the users based on de id of the harddisk
2. customer must contact your for a key
3. generate a key with the info from the customer
4. provide the key to the customer
This is a fairly safe methode but the customer needs to contact you on every install of the software.
Why go through the trouble of doing that when you would just have to go through and rewrite it for each client specifically if it going to be prated the it is going to be prated no one can control that you should jsut let it flow and not take the time to even go through the trouble of stopping it cause it will happen sorry to say but piracy is out there and if you try to stop it it will just get worse
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.