Skip to main content

Emita novamente o seu certificado de assinatura de código

Aprenda como re-emitir seu certificado de assinatura 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 EAL4+, or equivalent.

For more information, see our knowledge base articles:

Antes de começar

Caso esteja re-emitindo seu certificado de assinatura de código (CS) para a plataforma Sun Java, deverá enviar uma solicitação de assinatura de certificado (CSR) com seu pedido. Contudo, pode incluir uma CST com sua solicitação para qualquer plataforma.

Para permanecer seguro, os certificados devem usar um tamanho de chave RSA 3072 bits ou ECC P-256 bits ou maior. Para encontrar instruções sobre como criar um CSR para diferentes sistemas operacionais e plataformas, consulte Criar CSR para uma solicitação de certificado de assinatura 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.

Reemita seu certificado CS

  1. Na sua conta CertCentral, no menu principal à esquerda, clique em Certificado > Pedidos.

  2. Na página de Pedidos, clique no link do número do pedido para o certificado de assinatura de código que deseja re-emitir.

  3. Na página Detalhes do pedido, na lista suspensa Ações do certificado, selecione Reemitir certificado.

  4. A menos que você tenha um motivo específico para escolher um hash de assinatura diferente, a DigiCert recomenda usar o hash de assinatura padrão: SHA-256.

    1. Hash de assinatura

      A menos que você tenha um motivo específico para escolher um hash de assinatura diferente, a DigiCert recomenda usar o hash de assinatura padrão: 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 mailing 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 menu, 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 certificate signing request (CSR).

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

        2. In the Add your CSR box, upload or enter your CSR.

          Code signing certificates must use an RSA key a minimum of 3072 bits in length to remain secure.

          Your CSR must include the -----BEGIN NEW CERTIFICATE REQUEST----- and -----END NEW CERTIFICATE REQUEST----- tags.

        DigiCert send the certificate requester an agreement email. This email ensures the private key is stored on an HSM certified as FIPS 140 Level 2, Common Criteria EAL 4+, or equivalent. DigiCert can't issue the certificate unless 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.

      Don't have a compatible HSM?

      Select a different provisioning method. If you have any questions contact DigiCert Support.

    3. Motivo da reemissão

      Especifique a razão para a re-emissão do certificado.

  5. Clique em Solicitar reemissão.

E depois?

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.

Nesta secção: