コードサイニング証明書を再発行する
コードサイニング証明書を再発行する方法を学びます
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証明書を再発行する
CertCentralアカウントの左側にあるメインメニューで、[証明書]>[オーダー]の順にクリックします。
オーダーページで、再発行を希望するコードサイニング証明書のオーダー番号リンクをクリックします。
[オーダー詳細]ページにある[証明書アクション]ドロップダウンから、[証明書を再発行する]を選択します。
異なる署名ハッシュを選択する特定の理由がある場合を除いて、デジサートはデフォルトの署名ハッシュであるSHA-256の使用をお勧めします。
署名ハッシュ
異なる署名ハッシュを選択する特定の理由がある場合を除いて、デジサートはデフォルトの署名ハッシュであるSHA-256の使用をお勧めします。
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.
再発行の理由
証明書再発行の理由を入力します。
[再発行を申請する]をクリックします。
次のステップ
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.
DigiCert-provided hardware token (nonrefundable)
If you opted to have DigiCert send you a secure token, we send your token with instructions for installing the certificate on your token. See our knowledge base article for Installing your DigiCert® Code Signing Certificate onto a Secure Token.
Your own supported hardware token
If you 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 installing your code signing certificate on a supported HSM, download the certificate from CertCentral. See Download a code signing certificate from your account.