激活码
我不确定该问题的标题应该是什么，但我在这里寻求帮助。
我在一家公司工作，该公司在 CORE JAVA 平台上制作基于桌面的应用程序。 我们提供激活码来激活我们的软件。 激活的概念是——
<块引用>用户输入激活码 -->软件访问我们的服务器并下载所有必需的文件 -->激活完成。
我们的软件每天都会访问我们的服务器来检查激活码是否已过期。
问题- 我们有一个没有常规互联网连接的新客户。不知怎的，他们同意一次性提供互联网连接——
<块引用>用户输入激活码 -->软件访问我们的服务器并下载所有必需的文件 -->激活完成。
但之后就没有互联网连接了。我可以停止软件以向服务器检查激活码的到期日期。 但我的问题是-
1) 如何检查激活码是否实际上已过期？ （激活码有效期仅为1年）
2) 如果过期后用户输入新的激活码，我如何检查这是一个有效期为 1 年的有效激活码？
I am not sure what shall i put as Title for this Question, But I am here looking for help.
I work in a company which makes desktop based application on CORE JAVA Platform.
We provide an ACTIVATION CODE to activate our software.
The concept of activation is -
User enters the Activation code --> software hits our server and download all the required files --> activation completed.
Once in a day, our software hits our server to check if the activation code has been expired.
Problem-
We have a new client which doesn't have a regular internet connection. Somehow they agreed to provide internet connection for one time-
User enters the Activation code --> software hits our server and download all the required files --> activation completed.
but after that no internet connection. I can stop the software to check with server about expiry Date of activation code.
But the problem with me is-1) How do I check whether the Activation code has actually expired? ( Activation code is valid for 1 year only)
2) If after expiry If user enters a new Activation code, how do I check this is a valid activation code with 1 year validity?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
1）您可以存储注册日期并将其与系统日期进行比较。当然，用户可以调整日期。我曾经有一些软件总是存储它看到的最后一个日期，如果有人将日期移到过去，它就会抱怨并过期。你可以做这样的事情，但当然它永远不会像与服务器交谈那么安全。
2) 为您的激活密钥创建一种格式，其中包含新密钥以及以前的密钥。所以第一个键是 A，这有助于与服务器通信并检查 A 是否正常。新密钥可能看起来像 AB，意思是“我替换 A，再添加一年的激活，并称为 B，所以一年后，我们将需要像 BC 这样的密钥”。您必须考虑一下如何安全地对其进行编码，但我非常有信心它可以工作（例如，您可以用 A 加密 B，然后 B 只能在具有激活码 A 的计算机上使用）。
1) you can store the registration date and compare it against the system date. of course then users can temper with the date. I used to have some software that always stored the last date it had seen, and if one moved the date to the past, it complained and insta-expired. you could do something like this but of course it's never as safe as talking to a server.
2) create a format for your activation key that contains a new key as well as the previous key. so the first key is, say, A, which is good for talking to a server and checking if A is okay. A new key might look like AB meaning "I replace A, add another year of activation, and am called B, so in a year, we'll need a key like BC". You'll have to think a bit about how to encode this securely, but I'm pretty confident it can work (for example, you can encrypt B with A, then B can only be used on a machine with activation code A).