Skip to main content

Reemitir un certificado de firma de código EV

Conozca cómo volver a emitir su certificado de validación extendida (EV) de firma de código

Importante

El sector pasó a utilizar una clave RSA de 3072 bits como mínimo para los certificados de firma de código

Para cumplir con los cambios de la industria, DigiCert realizó los siguientes cambios en nuestro proceso de certificados de firma de código:

  • Solo emite certificados de firma de código RSA de 3072 bits o superiores*.

  • Utiliza nuevas CA intermedias y certificados raíz para emitir nuestros certificados de firma de código y de firma de código EV: RSA y ECC

DigiCert admite dos tokens electrónicos:

  • 5110 CC para certificados de clave RSA de 4096 bits y ECC P de 256 bits

  • 5110 FIPS para certificados de clave ECC P-256 y P-384 bits

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

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

HSM debe:

  • Admite tamaños de clave RSA de 3072 bits o ECC P-256 bits o superiores

  • Dispositivos compatibles con FIPS 140-2 Nivel 2+ o Common Criteria EAL4+

Más información sobre el cambio a los certificados de firma de código de clave de 3072 bits.

Antes de comenzar

Are you reissuing your EV Code Signing certificate for an HSM device?

Si está reemitiendo su certificado de firma de código EV para un dispositivo HSM, debe enviar una solicitud de firma de certificado (CSR) con su solicitud. Para mantener la seguridad, los certificados deben utilizar un tamaño de clave RSA de 3072 bits o ECC P-256 bits o superior. Consulte la documentación de su proveedor de HSM a fin de crear la CSR para su solicitud.

Para que sean seguros, los certificados deben tener una clave de, al menos, 2048 bits. Consulte la documentación de su proveedor de HSM a fin de crear la CSR para su solicitud.

Volver a emitir su certificado EV CS

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

  2. En la página Pedidos, en la columna N.° de pedido, haga clic en el enlace Vista rápida para el certificado EV de firma de código que desea volver a emitir.

  3. En el panel de información del N.° de pedido (a la derecha), haga clic en Reemisión del certificado.

  4. Solo para los dispositivos HSM: si usa un token seguro, pase al paso 5.

    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 will store the private key and certificate. For the security of your EV Code Signing certificate, the certificate must be installed on and used from an approved device.

      Select the storage device for your EV Code Signing certificate and its' private key.

      • DigiCert-provided hardware token.

        DigiCert ships you a secure token with instructions for installing the certificate on your token, so you can start signing code.

        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.

        After DigiCert issues your EV 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 EV Code Signing certificate:

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

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

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

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

        Importante

        You must have a FIPS 140-2 Level 2 or Common Criteria EAL4+ compliant device. See Currently Supported eTokens. You will not be able to install the certificate on any device that is not on the list.

        If you don't have one of the approved tokens, please select the option to have a preconfigured hardware token shipped to you. If you have any questions, please contact DigiCert Support.

      • Install on HSM.

        After DigiCert issues your EV 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?

        Note that we will send the certificate requestor an agreement email. This email is to ensure that a private key is stored on an HSM that is certified as FIPS 140-2 Level 2, Common Criteria EAL 4+, or equivalent. DigiCert will only issue the certificate 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, please contact DigiCert Support.

    3. Reason for reissue

      In the box, enter the reason for the certificate reissue.

  5. Haga clic en Solicitar reemisión.

Qué sigue

Approval for your EV Code Signing certificate reissue may be required

If a reissue approval is required, we email the EV Code Signing verified contacts for the organization, informing them that they need to approve the certificate reissue request. Once we receive their approval, we'll reissue your EV Code Signing certificate.

Certificate issuance

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

En esta sección: