处理 Visual Basic 2008 许可的代码
是否有可用于许可我的 Visual Basic 2008 应用程序的许可证？类似于 .Net Reactor，人们需要输入许可证密钥。有什么建议吗？
谢谢，
凯文。
Is there a license thing out there that can be used to license my application for Visual Basic 2008? Something like .Net Reactor, where the person needs to enter a license key. Any recommendations?
Thanks,
Kevin.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
不幸的是，有许多可能的许可机制。我过去使用过的一个是 CrypKey (http://www.crypkey.com/index.asp< /a>），但除非满足以下条件，否则我不会推荐它：
另外你的问题有点不清楚。许可主题有许多可能的变化。我所知道的最安全的纯软件解决方案是 CrypKey 实现的质询-响应类型，它与 Microsoft 的产品激活机制非常相似。有时您可能希望包括“免费试用”期。某些应用程序可能需要“并发使用”许可，并且需要在客户的计算机（或网络）上运行的服务器进程。有些只是使用在安装时输入的代码（通常包括某种形式的嵌入式序列号，以便可以检测到特定安装密钥的过度使用）。
这些天，我经常自己动手。这样就更容易了。请记住，您做得越复杂，您就越有可能因此接到服务电话。通常，我的确实使用质询-响应类型机制，其中质询部分基于用户或机器信息（例如许可用户的电子邮件地址、机器名称）的安全散列，并且响应是使用某种形式的安全单创建的方式转换（通常使用公钥/私钥对）。
希望这有帮助。
Unfortunately, there are many possible licensing mechanisms. One I have used in the past is CrypKey (http://www.crypkey.com/index.asp), but I wouldn't recommend it unless the following are true:
In addition your question is somewhat unclear. There are many possible variations on the theme of licensing. The most secure software-only solution I am aware of is the challenge-response type implemented by CrypKey which is very similar to Microsoft's product activation mechanism. Sometimes you may want to include a "free trial" period. Some applications may require "concurrent use" licensing and require a server process running on the customer's machine (or network). Some simply use a code entered at installation time (which will typically include some form of embedded serial number so over-use of a specific installation key can be detected).
These days, I often roll my own. It's just easier that way. Remember, the more complicated you make it the more likely you are to receive service calls because of it. Typically, mine do use a challenge-response type mechanism where the challenge part is based on a secure hash of either user or machine information (e.g. licensed user's email address, machine name), and the response is created using some form of secure one-way transformation (often using a public/private key pair).
Hope this helps.
如果您只需要一个简单的注册密钥验证机制，那么您应该考虑非对称加密，以避免注册机。或者，如果您不想打扰它，请尝试商业解决方案，例如 Ellipter - 它使用以下命令创建和验证序列椭圆曲线非对称加密，具有一些用于时间有限或用途有限的试验的类，并且它还可以将一些信息嵌入到创建的序列中，例如到期日期或产品信息。
If you need just a simple registration key verification mechanism then you should look at asymmetric encryption, to avoid keygens. Or if you don't want to bother with it then try a commercial solution, like Ellipter - it creates and verifies serials using elliptic curves asymmetric encryption, has some classes for time limited or usages limited trials and also it can embed some information into created serials, like expiration date or product info.