Skip to main content

Volver a emitir su certificado de firma de código

Conozca cómo volver a emitir su certificado de firma de código

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:

Antes de comenzar

Si vuelve a emitir su certificado de firma del código (CS) para la plataforma Sun Java, debe enviar una solicitud de firma de certificado (CSR) junto con su solicitud. No obstante, su solicitud puede ir acompañada de una CSR para cualquier plataforma.

Para mantener la seguridad, los certificados deben utilizar un tamaño de clave RSA de 3072 bits o ECC P-256 bits o superior. Para encontrar instrucciones sobre la creación de una CSR para diferentes sistemas operativos y plataformas, consulte Crear CSR para una solicitud de certificado de firma de código.

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.

Volver a emitir su certificado de CS

  1. En su cuenta de CertCentral, en el menú principal izquierdo, haga clic en Certificado > Pedidos.

  2. En la página Pedidos, haga clic en el enlace del número de pedido para el certificado de firma de código que desea volver a emitir.

  3. En la página Información del pedido, en el menú desplegable Acciones del certificado, elija Volver a emitir el certificado.

  4. A menos que tenga un motivo específico para elegir un hash de firma diferente, DigiCert recomienda usar el cifrado de firma predeterminado: SHA-256.

    1. Hash de firma

      A menos que tenga un motivo específico para elegir un hash de firma diferente, DigiCert recomienda usar el cifrado de firma predeterminado: 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.

        Importante

        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.

      Importante

      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. Motivo de la reemisión

      Indique la razón de la reemisión del certificado.

  5. Haga clic en Solicitar reemisión.

Qué sigue

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.

En esta sección: