Do you *mark* your products' installers?
Do you use any unique markers in your products' installers in order to track if some pirated version of your app starts circulating on the warez sites?
What I mean is: do you put some customer specific information in every installation before the customer downloads the software, then if later you discover your program on some warez site, you'll know exactly which user to talk to.
I'm still way to early to worry about such things, but I just wonder.
3 Answers
We actually add the customer information in the installers, making each installer unique. The reason is to make it easier for the users, not to track pirated copies.
I would not recommend it though. For us the choice was between having to several different installers, do some advanced scripting that alwasy would work on all OS combinations or to come up with a way to patch the included software (it took a while to get the vendors to agree to this).
The drawback is that you will have to build each installation from scratch or that you can't use most of the installers. We have found one installer that with a bit of tweaking allowed us to patch things into the exe-file while customer is downloading the file from our web server.
I would focus on making a good product and making the product as easy as possible for the users that want to pay for the it. Many users that would use a pirated copy wouldn't have bought your software anyway, they would just have used some other software. Isn't it better that they use yours? Some time in the future they might turn into a paying customer.
I'm not advocating to use pirated software. I'm just saying that a startup shouldn't worry to much about it. If it turns out to be a problem and that it is affecting the sales (i.e. it is easier to use a pirated version then to pay and use the real version) it is time to do something about it (probably to make it easier to buy and install the real version).
Finally:
The information about which copy that has been pirated is probably useless. Most customers are very loyal and don't leak copies to warez web sites intentionally. It is a lot more likely that someone copied the software without their knowledge.
Well, first of all, remember that if you trust your customers, they will be more likely to trust you. Also, I assume that you have considered the cost of piracy vs the cost of whatever scheme you choose for software keys.
Finally, ask yourself: if you did find out that a copy of customer X's software had made it onto a Warez site, what would you do then? You say you'd "talk" to them -- to what purpose? Legal action, etc.? You should consider the costs and benefits of whatever enforcement action you might take. Software tracking (a form of digital rights management/DRM) is a valid tool, but be sure that it makes sense in your particular case.
Now if you decide to do this, the standard way of doing it nowadays is via a product/license-key mechanism. Think of what Microsoft does with product keys, for example, or what most game software does with a license key. A license key will allow you to control who can use the software. Then when a license key becomes compromised/published, you will know exactly whose it is.
http://en.wikipedia.org/wiki/Product_key has more information on this mechanism.
-
That's not my point. First, I'm not going to sue anybody, simply because I don't have resources to do that. But sometimes just a official letter could do a miracles. Second, the user will not even aware that the installer they receive will contain such unique bytes - they just download "setup.exe" and that's all. – Krasimir Evtimov 15 years ago
-
And third, I don't see this as a way to control who can use my software. I'm well aware of thousands of license engines, but the problem is that once a cracker understand how to generate valid license number, he can generate as many numbers as he wants, and I will don't have any clue about who generate them. While, on the other hand, even if he generates new license number, he will still using and distributing the program installer itself. And that's why I came up with this idea - as a way to observe, not to control. – Krasimir Evtimov 15 years ago
-
And again, I didn't say that this was a good idea - I just want to discuss it with all of you in order to decide if it will pay off. – Krasimir Evtimov 15 years ago
-
Hi Krasimir, thanks for your further comments! In my case, it's not something I've done before, for the reasons I outline above. I prefer a license-key based mechanism when I do this. Your own opinion may certainly be different. In my opinion, knowing who distributed the software would be of little benefit. Sending them an official letter is too late -- they've already distributed the software. Also, I think that if you do this, you *should* tell the users, instead of keeping it secret. If the users know that you put an ID in the software, they'll be less likely to distribute it. -mark – Mark Beadles 15 years ago
Not sure how something like that would stand up in court if you were to pursue legal action but at least you would have the option.
If you pass the internal serial number to your server as part of a "check for update" feature it can also prove to be a way to track how your software gets disseminated / how many different machines a single license is installed on.
At some point though you cross the thin line between protecting yourself and invasion of privacy so I would be careful. Think about how you would react as a user.
Personally, I sell our software as a service which is the easiest way to protect your software. If that were not possible, would not bother with marking installers but instead focus more on making your software affordable and making it very easy to purchase a license. Facilitating honest use is easier than engaging software pirates in an arms race.
