android 许可：生成新密钥对时
我正在阅读 Android 应用程序许可。它使用密钥对来检查许可证。该文件还指出：
请注意，如果您出于某种原因决定为您的帐户生成新的许可密钥对，则需要通知测试帐户的所有用户。对于测试人员来说，您可以将新密钥嵌入到应用程序包中并将其分发给用户。对于开发人员，您需要将新密钥直接分发给他们。
我认为这与此服务器响应 LICENSED_OLD_KEY 有关：“应用程序已许可给用户，但有可用的更新应用程序版本，该版本使用不同的密钥签名。”
我理解这个概念。但是，我不清楚您何时需要生成新的许可密钥对。每当我们提交更新时，是否需要生成新的密钥对？我的猜测是否定的。我们什么时候需要生成新密钥？
I am reading Android Application Licensing. It uses a key pair to check license. The document also says that:
Note that if you decide to generate a new licensing key pair for your account for some reason, you need to notify all users of test accounts. For testers, you can embed the new key in the application package and distribute it to users. For developers, you will need to distribute the new key to them directly.
I think this is related to this server response LICENSED_OLD_KEY: "The application is licensed to the user, but there is an updated application version available that is signed with a different key. "
I understand this concept. However, what I am unclear about is when you would need to generate a new licensing key pair. Do we need to generate a new key pair whenever we submit an update? My guess is no. When do we need to generate a new key?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
不，您不需要每次发布更新时都生成新密钥。如果您的现有密钥由于某种原因（例如被盗）而被泄露，您只需要生成一个新密钥。
No, you do not need to generate a new key every time you release an update. You would only need to generate a new key if your existing key was compromised for some reason (e.g. stolen).