Re-emitir um certificado de assinatura de código EV
Aprenda como re-emitir seu certificado de assinatura de código com validação estendida (EV)
Importante
Indústria mudou para o mínimo de chave RSA de 3072 bits para certificados de assinatura de código
Para cumprir as mudanças do setor, a DigiCert fez as seguintes mudanças em nosso processo de certificado de assinatura de código:
Emite apenas chave RSA de 3072 bits ou certificados de assinatura de código maiores*
Usa novos certificados intermediários de CA e raiz para emitir nossos certificados de assinatura de código e de assinatura de código EV: RSA e ECC
DigiCert suporta dois eTokens:
5110 CC para certificados de chave RSA 4096 bits e ECC P-256 bits
5110 FIPS para certificados de chave ECC P-256 e 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.
O HSM deve:
Suportar tamanhos de chaves RSA 3072 bits ou ECC P-256 bits ou maiores
Ser dispositivos compatíveis com FIPS 140-2 Nível 2+ ou Common Criteria EAL4+
Saiba mais sobre a alteração para certificados de assinatura de código de chave de 3.072 bits.
Antes de começar
Are you reissuing your EV Code Signing certificate for an HSM device?
Se você estiver reemitindo seu certificado de assinatura de código EV para um dispositivo HSM, deverá enviar uma solicitação de assinatura de certificado (CSR) com sua solicitação. Para permanecer seguro, os certificados devem usar um tamanho de chave RSA 3072 bits ou ECC P-256 bits ou maior. Consulte a documentação do seu provedor HSM para criar o CSR para a sua solicitação.
Para permanecerem seguros, os certificados devem usar chaves de pelo menos 2048 bits. Consulte a documentação do seu provedor HSM para criar o CSR para a sua solicitação.
Reemita seu certificado EV CS
Na sua conta da CertCentral, no menu principal à esquerda, acesse Certificados > Pedidos.
Na página Pedidos, na coluna Nº do pedido, clique no link Visualização rápida do certificado de assinatura de código EV que você deseja reemitir.
No painel de detalhes do Nº do pedido (à direita), clique em Reemitir certificado.
Apenas para dispositivos HSM - se estiver usando token seguro, pule para a etapa 5.
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.
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 (nonrefundable)
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 listed above. You cannot install the certificate on any device not on the list.
Need an approved token?
Please select DigiCert-provided hardware token to have a token shipped to you. If you have 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.
Reason for reissue
In the box, enter the reason for the certificate reissue.
Clique em Solicitar reemissão.
E depois?
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.
DigiCert-provided hardware token (nonrefundable)
If you opted to have DigiCert send you a secure token, we ship your token with instructions for installing the certificate on your token, so you can start signing code. See our knowledge base article for Installing your DigiCert® Code Signing Certificate onto a Secure Token.
Your own supported hardware token
If you opted to use your own supported secure token, see our knowledge base article for Installing your DigiCert® Code Signing Certificate onto a Secure Token.
A supported HSM device
If you opted to install your EV code signing certificate on a supported HSM, download the certificate from your CertCentral account to install it on the HSM. See Download a code signing certificate from your account.