[英]How do you protect your software from illegal distribution?

I am curious about how do you protect your software against cracking, hacking etc.


Do you employ some kind of serial number check? Hardware keys?


Do you use any third-party solutions?


How do you go about solving licensing issues? (e.g. managing floating licenses)

您如何解決許可問題? (例如管理浮動許可證)

EDIT: I'm not talking any open source, but strictly commercial software distribution...


25 个解决方案



There are many, many, many protections available. The key is:


  • Assessing your target audience, and what they're willing to put up with
  • 評估您的目標受眾,以及他們願意忍受的內容

  • Understanding your audience's desire to play with no pay
  • 了解您的觀眾無需付費的願望

  • Assessing the amount someone is willing to put forth to break your protection
  • 評估某人願意提供的金額以打破您的保護

  • Applying just enough protection to prevent most people from avoiding payment, while not annoying those that use your software.
  • 應用足夠的保護措施,以防止大多數人避免付款,同時不會使那些使用您的軟件的人煩惱。

Nothing is unbreakable, so it's more important to gauge these things and pick a good protection than to simply slap on the best (worst) protection you are able to afford.


  • Simple registration codes (verified online once).
  • 簡單的注冊碼(在線驗證一次)。

  • Simple registration with revokable keys, verified online frequently.
  • 簡單注冊可重新啟動的密鑰,經常在線驗證。

  • Encrypted key holds portion of program algorithm (can't just skip over the check - it has to be run for the program to work)
  • 加密密鑰保存程序算法的一部分(不能只是跳過檢查 - 它必須運行才能使程序工作)

  • Hardware key (public/private key cryptography)
  • 硬件密鑰(公鑰/私鑰加密)

  • Hardware key (includes portion of program algorithm that runs on the key)
  • 硬件密鑰(包括在密鑰上運行的程序算法的一部分)

  • Web service runs critical code (hackers never get to see it)
  • Web服務運行關鍵代碼(黑客永遠不會看到它)

And variations of the above.





Whatever route you go, charge a fair price, make it easy to activate, give free minor updates and never deactivate their software. If you treat your users with respect they'll reward you for it. Still, no matter what you do some people are going to end up pirating it.





Pirates will pirate. No matter what solution you come up with, it can and will be cracked.


On the other hand, your actual, paying customers are the ones who are being inconvenienced by the crap.




Make it easier to buy than to steal. If you put mounds of copy protection then it just makes the value of owning the real deal pretty low.


Use a simple activation key and assure customers that they can always get an activation key or re-download the software if they ever lose theirs.


Any copy protection (aside from online-only components like multiplayer games and finance software that connects to your bank, etc.) you can just assume will be defeated. You want downloading your software illegally, at the very least, to be slightly harder than buying it.


I have a PC games that I've never opened, because there is so much copy protection junk on it that it's actually easier to download the fake version.




The Microsoft Software License scheme is crazy expensive for a small business. The server cost is around $12,000 if you want to set it up yourself. I don't recommend it for the feint of heart.


We actually just implemented Intellilock in our product. It lets you have all of the decisions for how strict you want your license to be, and it is very cost effective as well. In addition it does obfuscation, compiler prevention, etc.


Another good solution I have seen small/med businesses use is SoloServer. It is much more of an ecommerce and license control system. It is very configurable to the point of maybe a little too complex. But it does a very good job from what I have heard.


I have also used the Desaware license system for dot net in the past. It is a pretty lightweight system compared to the two above. It is a very good license control system in terms of cryptographically sound. But it is a very low level API in which you have to implement almost everything your app will actually use.




Software protections aren't worth the money -- if your software is in demand it will be defeated, no matter what.

軟件保護是不值得的 - 如果你的軟件需求它將被打敗,無論如何。

That said, hardware protections can work well. An example way it can work well is this: Find a (fairly) simple but necessary component of your software and implement it in Verilog/VHDL. Generate a public-private keypair and make a webservice that takes a challenge string and encrypts it with the private key. Then make a USB dongle that contains your public key and generates random challenge strings. Your software should ask the USB dongle for a challenge string and send it up to the server for encryption. The software then sends it to the dongle. The dongle validates the encrypted challenge string with the public key and goes into an 'enabled' mode. Your software then calls into the dongle any time it needs to do the operation you wrote in HDL. This way anyone wanting to pirate your software has to figure out what the operation is and reimplement it -- much harder than just defeating a pure software protection.

也就是說,硬件保護可以很好地工作。它可以很好地工作的一個示例方法是:找到一個(相當)簡單但必要的軟件組件,並在Verilog / VHDL中實現它。生成公共 - 私有密鑰對,並創建一個Web服務,該服務接受挑戰字符串並使用私鑰對其進行加密。然后制作一個包含公鑰的USB加密狗,並生成隨機挑戰字符串。您的軟件應該向USB加密狗詢問挑戰字符串並將其發送到服務器進行加密。然后軟件將其發送到加密狗。加密狗使用公鑰驗證加密的質詢字符串,並進入“啟用”模式。然后,只要需要執行您在HDL中編寫的操作,您的軟件就會調用加密狗。這樣,任何想要盜版軟件的人都必須弄清楚操作是什么並重新實現它 - 比打敗純軟件保護要困難得多。

Edit: Just realized some of the verification stuff is backwards from what it should be, but I'm pretty sure the idea comes across.




Digital "Rights" Management is the single biggest software snake-oil product in the industry. To borrow a page from classic cryptography, the typical scenario is that Alice wants to get a message to Bob without Charlie being able to read it. DRM doesn't work because in its application, Bob and Charlie are the same person!

數字“權利”管理是業內最大的軟件蛇油產品。借用經典密碼學中的頁面,典型的情況是Alice希望在沒有Charlie能夠閱讀的情況下向Bob發送消息。 DRM不起作用,因為在其應用中,Bob和Charlie是同一個人!

You would be better off asking the inverse question, which is "How do I get people to buy my software instead of stealing it?" And that is a very broad question. But it generally starts by doing research. You figure out who buys the type of software you wish to sell, and then produce software that appeals to those people.


The additional prong to this is to limit updates/add-ons to legit copies only. This can be something as simple as an order code received during the purchase transaction.


Check out Stardock software, makers of WindowBlinds and games such as Sins of a Solar Empire, the latter has no DRM and turned a sizable profit off a $2M budget.

查看Stardock軟件,WindowBlinds的制造商和Sins of a Solar Empire等游戲,后者沒有DRM,並從200萬美元的預算中獲得可觀的利潤。



There are several methods, such as using the processor ID to generate an "activation key."


The bottom line is that if someone wants it bad enough -- they'll reverse engineer any protection you have.

最重要的是,如果有人想要它足夠糟糕 - 他們將對你擁有的任何保護進行逆向工程。

The most failsafe methods are to use online verification at runtime or a hardware hasp.


Good luck!



Online-only games like World of Warcraft (WoW) have it made, everyone has to connect to the server every time and thus accounts can be constantly verified. No other method works for beans.




Is not exactly the answer you are looking for, but is a great resource on piracy from a game developer who actively asked their pirates about why they do that. And is related to the first part of the answer you choose.


Readi it at Talking to Pirates.




Generally there are two systems that often get confused -

通常有兩個系統經常混淆 -

  • Licensing or activation tracking, legal legitimate usage
  • 許可或激活跟蹤,合法合法使用

  • Security preventing illegal usage
  • 安全防止非法使用

For licensing use a commercial package, FlexLM many companies invest huge sums of money into licensing think they also get security, this is a common mistake key generators for these commercial packages are prolifically abundant.


I would only recommend licensing if your selling to corporations who will legitimately pay based on usage, otherwise its probably more effort than its worth.


Remember that as your products become successful, all and every licensing and security measure will be breached eventually. So decide now if it is really worth the effort.


We implemented a clean room clone of FlexLM a number of years ago, we also had to enhance our applications against binary attacks, its long process, you have to revisit it every release. It also really depends on which global markets you sell too, or where your major customer base is as to what you need to do.


Check out another of my answers on securing a DLL.




Given a little time your software will always be cracked. You can search for cracked versions of any well known piece of software in order to confirm this. But it is still well worth adding some form of protection to your software.


Remember that dishonest people will never pay for your software and always find/use a cracked version. Very honest people will always stick to the rules even without a licensing scheme just because that is the kind of person they are. But the majority of people are between these two extremes.


Adding some simple protection scheme is a good way of making that bulk of people in the middle act in an honest way. It is a way to nudge them into remembering that the software is not free and they should be paying for the appropriate number of licenses. Many people do actually respond to this. Businesses are especially good at sticking to the rules because the manager is not spending his/her own money. Consumers are less likely to stick to the rules because it is their own money.


But recent experience with releases such as Spore from Electronic Arts shows that you can go to far in licensing. If you make even legit people feel like criminals because they are constantly being validated then they start to rebel. So add some simple licensing to remind people if they are being dishonest but anything more than that is unlikely to boost sales.




DRM this, DRM that - publishers who force DRM on their projects are doing it because it's profitable. Their economists are concluding this on data which none of us will ever see. The "DRM is evil" trolls are going a little too far.

DRM,DRM - 在他們的項目中強制使用DRM的出版商正在這樣做,因為它有利可圖。他們的經濟學家正在對我們沒有人會看到的數據做出總結。 “DRM是邪惡的”巨魔有點太過分了。

For a low-visibility product, a simple internet activation is going to stop casual copying. Any other copying is likely negligible to your bottom line.




Illegal distribution is practically impossible to prevent; just ask the RIAA. Digital content can just be copied; analog content can be digitised, and then copied.


You should focus your efforts on preventing unauthorised execution. It's never possible to completely prevent the execution of code on someone else's machine, but you can take certain steps to raise the bar sufficiently high that it becomes easier to purchase your software than to pirate it.


Take a look at the article Developing for Software Protection and Licensing that explains how best to go about developing your application with licensing in mind.


Obligatory disclaimer & plug: the company I co-founded produces the OffByZero Cobalt software licensing solution for .NET.

強制免責聲明和插件:我共同創辦的公司生產用於.NET的OffByZero Cobalt軟件許可解決方案。



The trouble with this idea of just let the pirates use it they wont buy it anyway and will show their friends who might buy it is twofold.


  1. With software that uses 3rd party services, the pirated copies are using up valuable bandwidth/resource which gives legit users a worse experience, make my sw look more popular then it is and has the 3rd party services asking me to pay more for their services because of the bandwidth being used.


  2. Many casual wouldn't dream of cracking the sw themselves but if there is an easy assessible crack on a site like piratebay they will use it, if there wasn't they might buy it.


This concept of not disabling pirated software once discovered also seems crazy, I don't understand why I should let someone continue to use software they shouldn't be using, I guess this is just the view/hope of the pirates.


Also, its worth noting that making a program hard to crack is one thing, but you also need to prevent legit copies being shared, otherwise somebody could simply buy one copy and then
share it with thousands of others via a torrent site. The fact of having their name/email address embedded in the license isn't going to be enough to disuade everyone from doing this, and it only really takes one for there to be a problem.


The only way I can see to prevent this is to either:


  1. Have server check and lock license on program startup every time, and release license on program exit. If another client starts with same license whilst the first client has license then it is rejected. This way doesn't prevent the license being used by more than one user, but does prevent it being used concurrently by more than one user - which is good enough. It also allows a legitimate user to transfer the license on any of their computers which provides a better experience.

    每次在程序啟動時檢查並鎖定許可證,並在程序退出時釋放許可證。如果另一個客戶端使用相同的許可證啟動,而第一個客戶端具有許可證,則拒絕這種方式不會阻止多個用戶使用許可證,但會阻止多個用戶同時使用許可證 - 這已經足夠了。它還允許合法用戶在其任何計算機上傳輸許可證,從而提供更好的體驗。

  2. On first client startup client sends license to server and server verifies it, causing some flag to be set within the client software. Further requests from other clients with the same license are rejected. The trouble with this approach is the original client would have problems if they reinstalled the software or wanted to use a different computer.




Even if you used some kind of biometric fingerprint authentication, someone would find a way to crack it. There's really no practical way around that. Instead of trying to make your software hack-proof, think about how much extra revenue will be brought in by adding additional copy protection vs. the amount of time and money it will take to implement it. At some point, it gets to be cheaper to go with a less rigorous copy protection scheme.


It depends on what exactly your software product is, but one possibility is to move the "valuable" part of the program out of the software and keep it under your exclusive control. You would charge a modest fee for the software (mostly to cover print and distribution costs) and would generate your revenue from the external component. For example, an anti-virus program that is sold for cheap (or bundled for free with other products) but sells subscriptions to its virus definitions update service. With that model, a pirated copy that subscribes to your update service wouldn't represent much of a financial loss. With the increasing popularity of applications "in the cloud", this method is becoming easier to implement; host the application on your cloud, and charge users for cloud access. This doesn't stop someone from re-implementing their own cloud to eliminate the need for your service, but the time and effort involved in doing so would most likely outweigh the benefits (if you keep your pricing model reasonable).




As has been pointed out, software protection is never guaranteed to be foolproof. What you intend to use depends largely on your target audience. A game, for instance, is not something you are going to be able to protect forever. A server software, on the other hand, is something far less likely to be distributed on the Internet, for a number of reasons (product penetration and liability come to mind; a large corporation does not want to be held liable for bootleg software, and the pirates only bother with things in large-enough demand). In all honesty, for a high-profile game, the best solution is probably to seed the torrent yourself (clandestinely!) and modify it in some way (for instance, so that after two weeks of play it pops up with messages telling you to please consider supporting the developers by purchasing a legitimate copy).


If you put protection in place, bear two things in mind. First, a lower price will supplement any copy protection by making people more inclined to pay the purchase price. Secondly, the protection must not get in the way of users - see Spore for a recent example.

如果你保護到位,請記住兩件事。首先,較低的價格將通過讓人們更傾向於支付購買價格來補充任何版權保護。其次,保護不得妨礙用戶 - 請參閱Spore最近的一個例子。



The simple, and best solution, is just to charge them up front. Set a price that works for you and them.


Asking paying customers to prove that they are paying customers after they've already paid just pisses them off. Implementing the code to make your software not run wastes your time and money, and introduces bugs and annoyances for legitimate customers. You'd be better off spending that time making a better product.


Lots of games/etc will "protect" the first version, then drop the protections in the first patch due to compatibility problems with real customers. It's not an unreasonable strategy if you insist on a modicum of protection.




Almost all copy-protection is both ineffective, and a usability nightmare. Some of it, such as putting root-kits on your customers' machines becomes downright unethical




Make part of your product an online component which requires connection and authentication. Here are some examples:


  • Online Games
  • Virus Protection
  • Spam Protection
  • Laptop tracking software
  • 筆記本電腦跟蹤軟

This paradigm only goes so far though and can turn some consumers off.




If your interested in protecting software that you intend to sell to consumers I would recommend any of a variety of license key generating libraries (Google search on license key generation). Usually the user has to give you some sort of seed like their email address or name and they get back the registration code.


Several companies will either host and distribute your software or provide a complete installation/purchase application that you can integrate with and do this automatically probably at no additional cost to you.


I have sold software to consumers and I find this the right balance of cost/ease of use/protection.




I agree with a lot of posters that no software-based copy protection scheme will deter against a skilled software pirate. For commercial .NET based software Microsoft Software License Protection (SLP) is a very reasonably priced solution. It supports time-limited and floating licenses. Their pricing starts at $10/month + $5 per activation and the protection components seem to work as advertised. It's a fairly new offering, though, so buyer beware.




I suggest simple activation key (even if you know that it can be broken), you really don't want your software to get in your users way, or they'll simply push it away.


Make sure that they can re-download the software, I suggest a web page where they can logging and download your software only after they paid (and yes they should be able to download as many times they wish it, directly, without a single question about why on your part).


Thrust your paid users above all, there is nothing more irritating that being accused from being a criminal when you are a legit users (DVD's anti-piracy warnings anyone).


You can add a service that checks the key against a server when online, and in case of two different IPs are using the same key, popup a suggestion to buy another license.


But please don't inactivate it, it might be a happy user showing your software to a friend!!!!




If you are a software developer, one of the possible solutions is to embed a meta data direct into your product. Check out for an instance Destruction Security tool from theredsunrise.




We license our commercial software using our own licensing system - which is what we are selling (license management tools). We generally sell subscription licenses, but can also sell based on usage if we wish. It has been secure for us so far: www.agilis-sw.com

我們使用自己的許可系統許可我們的商業軟件 - 這是我們正在銷售的(許可管理工具)。我們通常出售訂閱許可證,但如果我們願意,也可以根據使用情況進行銷售。到目前為止,它對我們來說是安全的:www.agilis-sw.com



粤ICP备14056181号  © 2014-2021 ITdaan.com