通过激活/产品注册密钥进行保护 [英] Protection via activation / product registration keys
问题描述
嗨
任何人都可以提供创建注册码的任何提示/技巧/
应用程序激活，作为Winform的软件复制保护措施
用C＃开发的应用程序？
谢谢
Hi
Can anyone offer any hints / tips for creating registration keys /
application activation, as software copy protection measures for a Winform
app developed in C#?
Thanks
推荐答案
2005年1月29日星期六16:21： 15 GMT，Paul Aspinall < pa ** @ aspy.co.uk>
写道：
On Sat, 29 Jan 2005 16:21:15 GMT, "Paul Aspinall" <pa**@aspy.co.uk>
wrote:
嗨
任何人都可以提供创建注册码的任何提示/技巧/
应用程序激活，作为用C＃开发的Winform
应用程序的软件复制保护措施？
谢谢
Hi
Can anyone offer any hints / tips for creating registration keys /
application activation, as software copy protection measures for a Winform
app developed in C#?
Thanks
这个主题在sci.crypt中重复出现。谷歌为它。
普遍的共识是，这是浪费时间。
一个坚定的黑客将妥协任何版权保护
系统和一旦系统受到损害，就可以制作无限的b $ b b副本。这是一个单一的妥协
对系统是致命的。
微软花了大量的时间和金钱来解决问题和最好的
他们可以做的
会产生破坏的更新。受损的副本
下载它们。除非你打算花更多的时间和比微软更多的钱，所以要让合法用户轻松一点，并希望你的b / b
软件值得盗版。
Leslie''Mack''McBride
删除_标记之间的文字以通过电子邮件回复
This topic comes up repeatedly in sci.crypt. Google for it.
The general consensus is that it is a waste of time.
A determined hacker will compromise any copy protection
system and once the system is compromised an infinite
number of copies can be made. That is a single compromise
is fatal to the system.
Microsoft has spent a ton of time and money on the issue and the best
they can do is produce updates that "break" compromised copies that
download them. Unless you are planning on spending more time and
money than microsoft, make it easy on legitimate users and hope your
software is worth pirating.
Leslie ''Mack'' McBride
remove text between _ marks to respond via e-mail
Paul，
" Paul Aspinall" < PA ** @ aspy.co.uk> schrieb：
Paul,
"Paul Aspinall" <pa**@aspy.co.uk> schrieb:
任何人都可以提供任何关于创建注册码/
应用程序激活的提示/技巧，作为用C＃开发的Winform
应用程序的软件复制保护措施吗？
Can anyone offer any hints / tips for creating registration keys /
application activation, as software copy protection measures for a Winform
app developed in C#?
..NET'的授权机制：
..NET Framework开发人员指南 - 许可组件和控件
< URL：http：//msdn.microsoft.com/library/en-us/cpguide/html/cpconlicensingcomponentscontrols.asp>
..NET许可
< URL：http：//windowsforms.net/articles/Licensing.aspx>
商业组件：
XHEO |许可
< URL：http：//www.xheo.com/products/enterprise/licensing/>
-
MS Herfried K. Wagner
MVP< URL：http：//dotnet.mvps.org/>
VB< URL ：http：//dotnet.mvps.org/dotnet/faqs/>
..NET''s licensing mechanisms:
..NET Framework Developer''s Guide -- Licensing Components and Controls
<URL:http://msdn.microsoft.com/library/en-us/cpguide/html/cpconlicensingcomponentscontrols.asp>
..NET Licensing
<URL:http://windowsforms.net/articles/Licensing.aspx>
Commercial components:
XHEO|Licensing
<URL:http://www.xheo.com/products/enterprise/licensing/>
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
我经常使用许可密钥方法tha我发现非常安全。它b / b
涉及构建一长串数据，例如计算机
名称，用户名和其他指标对机器来说唯一的产品
将被安装。这个长字符串用于生成每个安装唯一的散列密钥
。在大多数情况下，我使用网络服务来生成密钥生成，以便在我的服务器的控制之下。
我创建了一个许可组件，使用此哈希键根据运行时/设计时使用授予或拒绝
许可证，我也做了可怕的事情
检查是否存在运行的不同类型的调试器
机器。这个许可组件被一个混淆器严重混淆
崩溃IL反汇编程序，并且它的内部也被加密，无论
可能。
我觉得我可以解释这一点，因为系统的核心取决于
这么多因素共同创造了一系列信息
平均值1000个字符。哈希密钥破解系统，例如查询
表，在15或20个字符之后是不可靠的，所以我认为我收集的所有
奇怪信息都非常安全。
IMO如果有人有能力破解这样一个可变系统，就像每个装置的每个装置不同，即使它已经安装了两次在
同一台机器上，那么他们是非常低百分比的人将会被无所畏惧。我知道单个破解需要花费很长时间才能获得
，关键是如此简单地改变，以至于我的部分更新将使黑客不得不离开通过整个反向
工程流程再次。
-
Bob Powell [MVP]
Visual C＃，System.Drawing
在Windows窗体中查找优秀的Windows窗体文章提示和技巧
http://www.bobpowell.net/tipstricks.htm
用GDI +回答那些GDI +问题常见问题
http://www.bobpowell.net/faqmain.htm
所有新文章都提供C＃和VB.NET中的代码。
订阅提供的RSS源，绝不会错过任何新文章。
" Paul Aspinall" < PA ** @ aspy.co.uk>在消息中写道
新闻：％J ***************** @ fe1.news.blueyonder.co.uk ...
I regularly use a license key method that I''ve found to be very safe. It
involves the construction of a long string of data such as the computer
name, user name and other metrics that are unique to the machine the product
is to be installed. This long string is used to generate a hash key that is
unique for every installation. In most instances I use a web-service to do
the key generation so that is under the control of my server.
I created a licensing component that uses this hash key to grant or deny
licenses based upon runtime / design time use and I also do horrible stuff
like check for the presence of different sorts of debugger running on the
machine. This licensing component is heavily obfuscated with an obfuscator
that crashes the IL disassemblers and it''s guts are also encrypted wherever
possible.
I feel that I can explain this because the heart of the system depends upon
so many factors that go together to create a string of information which
averages about 1000 characters. Hash key cracking systems such as lookup
tables are unreliable past 15 or 20 characters so my strings with all the
weird information I collect are, I think, quite safe.
IMO If anyone has the energy to crack such a variable system as one that is
different for each and every installation, even if it''s installed twice on
the same machine, then they are the very low percentage of people who will
be deterred by nothing. I know that a single crack would take an
inordinately long time and the key is so simple to change that a trivial
update on my part will make the hackers have to go through the whole reverse
engineering process again.
--
Bob Powell [MVP]
Visual C#, System.Drawing
Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm
Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm
All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
"Paul Aspinall" <pa**@aspy.co.uk> wrote in message
news:%J*****************@fe1.news.blueyonder.co.uk ...
嗨
任何人都可以提供创建注册码/
应用程序激活的任何提示/技巧，作为用C＃开发的Winform
应用程序的软件复制保护措施吗？
谢谢
Hi
Can anyone offer any hints / tips for creating registration keys /
application activation, as software copy protection measures for a Winform
app developed in C#?
Thanks
这篇关于通过激活/产品注册密钥进行保护的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
