Skip to main content

补发代码签名证书

了解如何补发代码签名证书

New private key storage requirements

On May 30, 2023, DigiCert updated our private key storage requirements for code signing certificate private keys, per industry standards. All private keys for code signing certificates must be stored on hardware certified as Federal Information Processing Standards (FIPS) 140-2 Level 2, Common Criteria EAL 4+, or equivalent.

For more information, see our knowledge base articles:

在开始之前

如果要为 Sun Java 平台补发代码签名 (CS) 证书，必须通过请求提交证书签名请求 (CSR)。但是，您可以在请求中包含任何平台的 CSR。

为了保持安全，证书必须使用最低 RSA 3072 位或 ECC P-256 位密钥大小。如需查找关于为不同的操作系统和平台创建 CSR 的说明，请参阅为代码签名证书请求创建 CSR。

HSM devices require you to submit a CSR with your request. The code signing secure token provisioning methods don't include an option for submitting a CSR.

补发 CS 证书

  1. 在您的 CertCentral 帐户的左侧主菜单中，单击证书 > 订单。

  2. 在“订单”页，单击您要补发的代码签名证书的订单编号链接。

  3. 在订单详情页面的证书操作下拉列表中，选择补发证书。

  4. 除非您有特定的原因选择其他签名哈希，否则 DigiCert 建议使用默认签名哈希：SHA-256。

    1. 签名哈希

      除非您有特定的原因选择其他签名哈希，否则 DigiCert 建议使用默认签名哈希：SHA-256。

    2. Provisioning method

      The provisioning method refers to where you store the private key and certificate. For the security of your code signing certificate, the certificate must be installed on and used from an approved device.

      Select the storage device for your code signing certificate and its' private key.

      • DigiCert-provided hardware token (nonrefundable)

        DigiCert sends you a secure token with instructions for installing the certificate on your token.

        Then, under Shipping address, add your shipping information: your name and the address where you want us to send the hardware token.

      • Use existing token

        When DigiCert issues your code signing certificate, you need to install the certificate on your token.

        In the Platform dropdown, select the type of hardware token on which you plan to install your code signing certificate:

        • SafeNet eToken 5110 CC (940) for RSA 4096-bit and ECC P-256-bit key certificates.

        • SafeNet eToken 5110 FIPS for ECC P-256-bit key certificates.

        • SafeNet eToken 5110+ FIPS for RSA 4096-bit and ECC P-256-bit key certificates.

        • SafeNet eToken 5110+ CC (940B) for ECC P-256-bit key certificates.

        • SafeNet eToken 5110+ CC (940C) for RSA 4096-bit and ECC P-256-bit key certificates.

        重要

        You must have a DigiCert supported FIPS 140-2 Level 2 or Common Criteria EAL4+ compliant device. You can’t install the certificate on any device not on the list.

        Select DigiCert-provided hardware token to have us send you a token. If you have questions, contact DigiCert Support.

      • Install on HSM

        When DigiCert issues your code signing certificate, install it on the HSM where you generated the private key and CSR.

        Select Yes under Was the private key generated by a Common Criteria EAL4+ standard or FIPS 140-2 level 2 HSM?

        For HSMs, we send the requester an agreement email. This email ensures that a private key is stored on an HSM certified as FIPS 140-2 Level 2, Common Criteria EAL 4+, or equivalent. DigiCert issues the certificate only after the requester agrees to the private key protection requirement.

      重要

      You must have a FIPS 140-2 Level 2, Common Criteria EAL 4+, or equivalent hardware security module (HSM) that supports at least 3072-bit keys.

      Select a different provisioning method if you don't have a compatible HSM. If you have any questions contact DigiCert Support.

    3. 补发原因

      指定补发证书的原因。

  5. 单击申请补发。

接下来

Approval for your code signing certificate reissue may be required

If a reissue approval is required, we email the code signing verified contacts for the organization. We inform them that they need to approve the certificate reissue request. When we receive their approval, we reissue your code signing certificate.

Certificate issuance

When the validation is done and the order is verified-contact approved, we issue your certificate. Then you can install your certificate on your hardware token or HSM.

本节内容如下: