您如何保護您的軟件免受非法分發?

[英]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 个解决方案

#1


67  

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.

以及上述的變化。

-Adam

#2


27  

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.

無論您走哪條路線,都要收取合理的價格,輕松激活,提供免費的小更新,永遠不要停用他們的軟件。如果您尊重用戶,他們會獎勵您。不過,無論你做什么,有些人最終會盜版它。

#3


24  

Don't.

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.

另一方面,您的實際付費客戶是那些被廢話困擾的客戶。

#4


22  

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.

我有一個我從未打過的PC游戲,因為它上面有很多版權保護垃圾,下載假版本實際上更容易。

#5


15  

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.

微軟軟件許可證計划對於小型企業來說是非常昂貴的。如果你想自己設置,服務器成本約為12,000美元。我不推薦它用於佯攻。

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.

我們實際上剛剛在我們的產品中實現了Intellilock。它可以讓您做出有關您希望獲得許可的嚴格程度的所有決策,並且它也非常具有成本效益。另外它還有混淆,編譯器預防等。

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.

我見過的小型/中型企業使用的另一個好方法是SoloServer。它更像是一個電子商務和許可控制系統。它非常易於配置,可能有點過於復雜。但是從我聽到的情況來看,它做得非常好。

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.

我過去也使用過網絡的Desaware許可證系統。與上述兩個相比,它是一個非常輕量級的系統。就加密聲音而言,它是一個非常好的許可控制系統。但它是一個非常低級的API,您必須實現您的應用程序實際使用的幾乎所有內容。

#6


14  

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.

編輯:剛剛意識到一些驗證的東西是從它應該是的倒退,但我很確定這個想法會遇到。

#7


9  

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萬美元的預算中獲得可觀的利潤。

#8


6  

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

有幾種方法,例如使用處理器ID生成“激活密鑰”。

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!

#9


3  

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.

像魔獸世界(WoW)這樣的在線游戲,每個人都必須每次都連接到服務器,因此可以不斷驗證帳戶。沒有其他方法適用於bean。

#10


3  

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.

在與海盜交談時閱讀它。

#11


3  

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.

對於許可使用商業軟件包,FlexLM許多公司投入大量資金進入許可認為他們也獲得了安全性,這是一個常見的錯誤,這些商業軟件包的關鍵生成器非常豐富。

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.

我們多年前實現了FlexLM的潔凈室克隆,我們還必須增強我們的應用程序以防止二進制攻擊,它的漫長過程,你必須在每個版本重新訪問它。這也取決於您銷售的全球市場,或您的主要客戶群在哪里,您需要做什么。

Check out another of my answers on securing a DLL.

查看我關於保護DLL的另一個答案。

#12


2  

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.

但是最近在電子藝術公司發布Spore的經歷表明,你可以在許可方面走得更遠。如果你讓合法的人感覺像犯罪分子,因為他們經常被證實,那么他們就會開始反抗。因此,添加一些簡單的許可,以提醒人們,如果他們是不誠實的,但除此之外的任何東西不太可能促進銷售。

#13


2  

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.

對於低可見性產品,簡單的互聯網激活將停止隨意復制。任何其他復制對您的底線來說可能是微不足道的。

#14


2  

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.

實際上無法防止非法分發;只要問RIAA。數字內容可以復制;模擬內容可以數字化,然后復制。

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軟件許可解決方案。

#15


2  

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.

    許多休閑人員不會夢想破解sw本身但如果在像piratebay這樣的網站上有一個容易的可評估的破解,他們會使用它,如果沒有他們可能會購買它。

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.

此外,值得注意的是,使程序難以破解是一回事,但您還需要防止合法副本被共享,否則有人可以簡單地購買一個副本,然后通過torrent網站與數千個其他副本共享。在許可證中嵌入他們的名字/電子郵件地址這一事實並不足以阻止所有人這樣做,而且只需要一個就可以解決問題。

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.

    在第一個客戶端啟動客戶端向服務器發送許可證,服務器驗證它,導致在客戶端軟件中設置一些標志。具有相同許可證的其他客戶的進一步請求將被拒絕。這種方法的問題是原始客戶端如果重新安裝軟件或想要使用其他計算機會遇到問題。

#16


2  

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).

這取決於您的軟件產品究竟是什么,但有一種可能性是將程序的“有價值”部分移出軟件並將其置於您的獨家控制之下。您將收取適當的軟件費用(主要用於支付打印和分發費用),並從外部組件產生收入。例如,一種廉價銷售的防病毒程序(或與其他產品免費捆綁銷售),但銷售其病毒定義更新服務的訂閱。使用該模型,訂閱您的更新服務的盜版副本不會造成很大的經濟損失。隨着“在雲中”應用程序的日益普及,這種方法變得越來越容易實現;在雲上托管應用程序,並向用戶收取雲訪問權限。這並不能阻止某人重新實施自己的雲以消除對您服務的需求,但這樣做所花費的時間和精力很可能超過收益(如果您保持定價模式合理)。

#17


1  

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最近的一個例子。

#18


1  

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.

許多游戲/等將“保護”第一個版本,然后由於與真實客戶的兼容性問題而放棄第一個補丁中的保護。如果你堅持一點點保護,這不是一個不合理的策略。

#19


1  

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

幾乎所有的版權保護都是無效的,也是一種可用性的噩夢。其中一些,例如在客戶的機器上放置root工具包就變得非常不道德

#20


0  

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.

這種模式只是走了這么遠,可以讓一些消費者失望。

#21


0  

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.

如果您有興趣保護您打算銷售給消費者的軟件,我會推薦各種許可證密鑰生成庫(Google搜索許可證密鑰生成)。通常,用戶必須為您提供某種種子,例如他們的電子郵件地址或姓名,他們會返回注冊碼。

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.

我已經向消費者銷售軟件,我發現這是成本/易用性/保護的正確平衡。

#22


0  

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.

我同意很多海報,沒有基於軟件的復制保護方案會阻止熟練的軟件盜版。對於基於.NET的商業軟件,Microsoft軟件許可保護(SLP)是一種價格非常合理的解決方案。它支持有時間限制和浮動許可證。它們的定價從每個10美元/月+每次激活5美元開始,保護組件似乎按照宣傳的方式工作。不過,這是一個相當新的產品,所以買家要小心。

#23


0  

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).

最重要的是推動你的付費用戶,當你是一個合法的用戶時,沒有什么比這更令人惱火的了(DVD的反盜版警告任何人)。

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.

您可以添加在線時檢查服務器密鑰的服務,如果兩個不同的IP使用相同的密鑰,則彈出建議購買另一個許可證。

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

但請不要停用它,它可能是一個快樂的用戶向朋友展示你的軟件!!!!

#24


0  

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.

如果您是軟件開發人員,可能的解決方案之一是將元數據直接嵌入到您的產品中。查看來自theredsunrise的實例銷毀安全工具。

#25


0  

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


注意!

本站翻译的文章,版权归属于本站,未经许可禁止转摘,转摘请注明本文地址:https://www.itdaan.com/blog/2008/09/21/720d33be47db0ceaa643b556fb809def.html



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