使用 spc 文件签署 adobe air 应用程序
我最近从 GoDaddy 购买了数字证书来签署 Adobe Air 应用程序。 GoDaddy，可能还有其他一些 CA，以 SPC 文件形式提供证书。但是，大多数有关编译和签署 Air 应用程序的信息都假设您有一个 p12 文件。我花了一些时间弄清楚如何处理这个问题，并认为与 SO 社区分享该过程会很好。我很快就会发布答案。
I recently purchased a digital certificate from GoDaddy to sign an adobe air application. GoDaddy, and probably some of the other CAs out there, deliver their certificates as SPC files. However, most of the information about compiling and signing an air application assumes you have a p12 file. I spent a while figuring out how to deal with this issue and thought it'd be good to share the process with the SO community. I will post an answer shortly.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
提出正确方法的关键是理解 p12 文件是一个密钥库 - 而不仅仅是一个证书。密钥库包含密钥和证书。签署 adobe air 应用程序时，您需要提供密钥库而不仅仅是证书。那么，让我从头开始。
第 1 步：创建密钥库
第 2 步：创建证书请求
第 3 步：使用之前创建的 CSR 从 CA 购买证书步。就我而言，我将证书下载为 SPC 文件。
第 4 步：将证书添加到您的密钥库
第 5 步：当前您的密钥库是 java 密钥库 (JKS)。将其转换为 PKCS12
第 6 步：签署您的应用程序
我认为也可以跳过第 5 步并使用 JKS 密钥库执行第 6 步。然而，我并没有确认这是否有效。
The key to coming up with the correct method was understanding that a p12 file is a keystore - not just a certificate. A keystore contains the key and the certificate. When signing an adobe air app, you need to provide a keystore and not just a certificate. So, let me begin from the top.
Step 1: Create a keystore
Step 2: Create a certificate request
Step 3: Purchase a certificate from a CA using the CSR created in the previous step. In my case, I downloaded the certificate as an SPC file.
Step 4: Add the certificate to your keystore
Step 5: Currently your keystore is a java key store (JKS). Convert this to PKCS12
Step 6: Sign your app
I think it's probably also possible to skip step 5 and perform step 6 using the JKS keystore. I didn't confirm that this works, however.