任何类型的加密证书许可证在 Mono 上都应该至少与在 Windows 上一样安全。 在没有证书的情况下部署应用程序。 如果未检测到证书，则其处于“缩减功能”模式。 如果是，则其处于“完整模式”。 仅在购买时颁发证书。 对于全功能的限时试用，您会遇到更大的问题，但最终，没有什么可以阻止用户弄乱他们的注册表，甚至在虚拟机中运行应用程序或使用系统随意恢复。
Any kind of encrypted certificate license ought to be at least as secure on Mono as it is on Windows. Deploy the app without the certificate. If it doesn't detect the certificate, its in 'reduced functionality' mode. If it does, then its in 'full mode'. Only issue certificate on purchase. For full-functionality-time-limited trials you run into a bigger problem, but at the end of the day, there was nothing stopping the user from messing with their registry, even to the extent of running your app in a VM or using System Restore liberally.
然而，Linux 上的注册表只是用户主目录中的一个文件，因此您实际上无法从 Mono 外部修改它，例如从 .msi 修改它（例如，.msi 在 Linux 上不存在） 。
The registry is available to you using the standard .Net Registry classes. You can write your encrypted values there, and retrieve them later.
However, the registry on Linux is just a file in the user's home directory, so what you can't really do is modify it from outside Mono, like from a .msi (as an example, .msi's don't exist on Linux).
You could always encrypt a file based on the CPUID and store it in the directory. I am not sure how storing a file on the hard drive is different than storing something in the registr. A user could still find the registry key export / import it as needed. It would be restricted to that machine only if you use the CPUID or Motherboard information to encrypt the data with.
发布评论
评论（3）
任何类型的加密证书许可证在 Mono 上都应该至少与在 Windows 上一样安全。 在没有证书的情况下部署应用程序。 如果未检测到证书，则其处于“缩减功能”模式。 如果是，则其处于“完整模式”。 仅在购买时颁发证书。 对于全功能的限时试用，您会遇到更大的问题，但最终，没有什么可以阻止用户弄乱他们的注册表，甚至在虚拟机中运行应用程序或使用系统随意恢复。
Any kind of encrypted certificate license ought to be at least as secure on Mono as it is on Windows. Deploy the app without the certificate. If it doesn't detect the certificate, its in 'reduced functionality' mode. If it does, then its in 'full mode'. Only issue certificate on purchase. For full-functionality-time-limited trials you run into a bigger problem, but at the end of the day, there was nothing stopping the user from messing with their registry, even to the extent of running your app in a VM or using System Restore liberally.
您可以使用标准 .Net 注册表类来使用该注册表。 您可以在那里写入加密值，并稍后检索它们。
然而，Linux 上的注册表只是用户主目录中的一个文件，因此您实际上无法从 Mono 外部修改它，例如从 .msi 修改它（例如，.msi 在 Linux 上不存在） 。
The registry is available to you using the standard .Net Registry classes. You can write your encrypted values there, and retrieve them later.
However, the registry on Linux is just a file in the user's home directory, so what you can't really do is modify it from outside Mono, like from a .msi (as an example, .msi's don't exist on Linux).
您始终可以根据 CPUID 加密文件并将其存储在目录中。 我不确定在硬盘驱动器上存储文件与在寄存器中存储文件有何不同。 用户仍然可以根据需要找到注册表项导出/导入。 仅当您使用 CPUID 或主板信息来加密数据时，它才会仅限于该机器。
You could always encrypt a file based on the CPUID and store it in the directory. I am not sure how storing a file on the hard drive is different than storing something in the registr. A user could still find the registry key export / import it as needed. It would be restricted to that machine only if you use the CPUID or Motherboard information to encrypt the data with.