作为一家公司，我可以购买单个证书来签署多个 Adobe AIR 应用程序以及这些应用程序的版本吗？
我真的希望我误解了将证书应用于 Adobe AIR 应用程序。证书对于我的预算来说很贵，上次我检查时大约是 300 美元或更多。我还不太了解这个过程，但看起来我必须为单个应用程序的单个版本购买证书。我相信这被称为代码签名证书。并且，它证明自证书颁发以来代码未曾更改。我可以理解，从各种来源下载应用程序的客户可能会因为知道代码没有更改而感到安全，但如何发布新的认证版本呢？每次更新代码时都必须购买另一个证书吗？或者我是否拥有该证书一段时间，并且可以随意使用它来签署新代码？我可以使用同一个证书签署多个应用程序吗？我无法想象必须为我公司的所有应用程序和较小的版本更改购买大量证书。
I really hope I'm misunderstanding applying certificates to Adobe AIR applications. Certificates are expensive for my budget at around $300 or more last I checked. I don't quite understand the process yet, but it reads like I must purchase a certificate for a single version of a single application. I believe it is called code-signing certificate. And, it certifies that the code hasn't been altered since the certificate was issued. I can understand how customers downloading the application from various sources might feel safe knowing the code hasn't changed, but how do I release new certified versions? Must I buy another certificate each time I update the code? Or do I own the certificate for a period of time and can use it to sign new code at my liesure? Can I use the same certificate to sign several applications? I can't imagine having to buy lots of certificates for all of my company's applications and ever minor version change.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
代码签名证书不是用于验证代码自颁发证书以来未发生更改，而是用于验证代码自“签名”以来未发生更改。差别很大。
特定证书与特定作品或该作品的版本无关。它与身份联系在一起。
代码签名证书的另一个目的是验证签署它的组织的身份。它是为了验证该应用程序确实来自经过验证的个人/组织，以便您知道您可以信任它。
因此，当您签署某些代码时，您是在让用户知道是您提供该代码，并且该代码自您签署以来并未发生更改。
这意味着您没有理由不能使用相同的证书来签署多个应用程序的多个版本，因为您正在验证的是您的组织身份。
此外，使用与先前版本相同的证书进行更新实际上很重要，否则可能会破坏应用程序。更改应用程序证书需要一个过程。
证书会在一段时间后过期，因此您需要偶尔更新证书。
希望这有帮助。
A Code Signing certificate is not for verifying that the code has not changed since the certificate was issued, it's to verify that the code has not changed since the code was "signed". Big difference.
A specific certificate is not tied to a particular piece of work, nor to a version of that work. It is tied to an identity.
The OTHER purpose of a code signing certificate is to verify the identity of the organization that signed it. It is to verify that the application actually came from a verified person/organization, so you know you can trust it.
So when you sign some code you are letting the user know that it is YOU that is providing that code and that the code has not changed since you signed it.
That means that there is no reason that you could not use the same certificate to sign multiple versions of multiple applications, because it is your organizations identity that you are verifying.
Also, it is actually important that you use the same certificate for an update as you do for the previous version or you can break the application. Changing an applications certificate has a bit of a process to it.
Certificates do expire after a time, so you will need to update the certificates once-in-a-while.
Hope this helps.