Skip to main content

Code Signing-Zertifikat verlängern

Sie müssen Ihr DigiCert-Code Signing-Zertifikat verlängern? Befolgen Sie die Schritte unter zur Verlängerung Ihres Zertifikats.

CertCentral changes for new private key storage requirements

Starting June 1, 2023, industry standards require private keys for Code Signing certificates to be stored on hardware certified as FIPS 140-2 level 2, Common Criteria EAL 4+, or equivalent.

To comply with the new requirement, DigiCert made the following changes that affect orders placed in CertCentral or via the Services API:

  • Must use one of the new hardware token and hardware security module (HSM) provisioning methods when ordering or renewing a code signing certificate.

  • DigiCert no longer accepts Code Signing certificate requests using a provisioning method that does not meet the new private key storage requirement. This includes new, renewal, and reissue requests.

  • DigiCert no longer issues Code Signing certificates using a provisioning method that does not meet the new private key storage requirement. This includes new, renewal, and reissue requests.

For more information, see our knowledge base articles:

SCHRITT 1: Eine neue CSR generieren (optional)

Wichtig

Umstellung auf Code Signing-Zertifikate mit mindestens 3072-Bit-RSA-Schlüssel durch die Branche

Um den Änderungen in der Branche zu entsprechen, hat DigiCert die folgenden Änderungen an unserem Code-Signing-Zertifikatsprozess vorgenommen:

  • Wir stellen nur noch Code-Signing-Zertifikate mit einem RSA-Schlüssel von 3072 Bit oder höher aus.*

  • Wir verwenden neue Zwischenzertifikate und Stammzertifikate für die Ausstellung unserer Code-Signing- und EV-Code-Signing-Zertifikate: RSA und ECC

*Note: All existing 2048-bit key code signing certificates issued before June 1, 2021, will remain active. You can continue to use these certificates to sign code until they expire.

Erfahren Sie mehr über die Umstellung auf Code Signing-Zertifikate mit 3072-Bit-Schlüssel.

  • Organization validation

    • Code Signing certificate renewals: Make sure the organization with which you want to associate your Code Signing (CS) certificate has been validated for CS – Code Signing Organization Validation.

    • EV Code Signing certificate renewals: Make sure the organization with which you want to associate your EV Code Signing certificate has been validated for EV CS – Code Signing Organization Extended Validation.

  • Domain validation (Code Signing certificate renewals only)

    When adding an email address as the subject of a code signing certificate, the email address must include a validated domain associated with the organization included in your order. Only validated domains appear on the order form.

    For example, if you want to add john.doe@example.com, make sure example.com has been validated. See Domain prevalidation.

  • Hardware security module (HSM)

    Are you installing your code signing certificate on an HSM device?

    Erforderlich: Die Sun Java Platform ist die einzige Plattform, für die Sie eine CSR einreichen müssen.

SCHRITT 3: Ausfüllen des Verlängerungsformulars

  1. Klicken Sie im linken Hauptmenü auf Zertifikate > Ablaufende Zertifikate.

  2. Klicken Sie auf der Seite Ablaufende Zertifikate neben dem zu verlängernden Zertifikat auf Jetzt verlängern.

  3. On the Order details page, in the Certificate actions dropdown, select Renew.

  4. On the Renew EV Code Signing/Code Signing Order page, update the renewal form as needed, including selecting a new provisioning method.

  5. Provisioning options

    The provisioning method refers to where you will 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 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 certificate, you must install it 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 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.

      Wichtig

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

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

    • Install on HSM.

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

      Wichtig

      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.

  6. When ready, select Submit request.

SCHRITT 4: DigiCert stellt das Code Signing-Zertifikat aus.

Falls Sie eine CSR eingereicht haben, senden wir das verlängerte Zertifikat per E-Mail an den Zertifikatskontakt. Sie können auch das verlängerte Zertifikat in Ihrem Konto herunterladen.

Complete organization validation

Before DigiCert can issue your certificate, we need to validate your authority to order a certificate for the organization on your code signing certificate. A validation agent will call a verified phone number to speak with someone who represents you (the certificate requestor) and can confirm your authority:

  • Human resources

  • Manager

  • Technical contact

Order approval

After DigiCert completes the required validation for your order, we send an email with information about how to approve the certificate request to the verified contacts included in the renewal. We can finish processing your order only after a verified contact approves your request.

Certificate issuance

Once the validation is complete and the order is verified-contact approved, we will issue your certificate.

In diesem Abschnitt: