加密产品密钥：公钥和私钥加密 [英] Encryption Product Keys : Public and Private key encryption

问题描述

我需要生成和验证产品密钥，并一直在考虑使用公钥/私钥系统。

I need to generate and validate product keys and have been thinking about using a public/private key system.

根据

• 生成我们的产品密钥，客户端名称是一个可变长度的字符串）


• 一个6位数的序列号。

如果产品密钥的管理长度（16个字符左右），那将是很好的

It would be good if the product key would be of a manageable length (16 characters or so)

我需要在基础上进行加密，然后分发解密/验证系统。由于我们的系统是用托管代码（.NET）编写的，我们不想分发加密系统，只能解密。我需要一个公共私钥似乎是一个很好的方法，使用我保存的一个密钥进行加密，并分发解密/验证所需的其他密钥。

I need to encrypt them at the base and then distrubute the decryption/validation system. As our system is written in managed code (.NET) we dont want to distribute the encryption system, only the decryption. I need a public private key seems a good way to do this, encrypt with the one key that i keep and distribute the other key needed for decrpytion/verification.

什么是一个适当的机制，以上述要求做到这一点？

What is an appropriate mechanism to do this with the above requirements?

注意：不要停止盗版;这是为了减少新手安装不需要/未经授权使用的组件的可能性。

推荐答案

以各种方式进行公开密钥加密，例如 http://msdn.microsoft.com /en-us/library/ms867080.aspx 。话虽如此，您所获得的只有一些信心，即完全访问发布的代码的人将无法发布自己的产品密钥。这些都不会阻止他们修补客户端以接受任何作为有效的密钥。这就是混淆所在。

.NET supports public key encryption in various ways, such as http://msdn.microsoft.com/en-us/library/ms867080.aspx. Having said this, all you'd gain is some confidence that someone with full access to the released code would not have the ability to issue their own product keys. None of this stops them from patching the client to accept anything as a valid key. That's where obfuscation fits in.

这篇关于加密产品密钥：公钥和私钥加密的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！