Pengguna baharuPelan DNS dan CDN percuma untuk setiap akaun baharu.Cipta akaun anda
Log masukDaftar percuma
Dokumentasi
Konsol

Code signing certificates: overview and ordering

The code signing products, OV vs EV, what to prepare, the vetting process and how to sign once issued.

4 minit bacaan Dikemas kini 6 Okt 2026

This page describes the code signing certificates Yeap Cloud offers, the difference between OV and EV, what to prepare before ordering, and the process from order to issuance.

Why sign your code

When unsigned programs are downloaded or installed, operating systems and browsers usually show warnings such as "Unknown publisher", and some corporate environments block them outright. Code signing:

  • Shows a CA-verified publisher (your organization's name) in installation prompts.
  • Guarantees the file has not been modified since it was signed; any change invalidates the signature.
  • With a timestamp, keeps the signature valid after the certificate expires (provided you timestamp when signing).

Products

Open Certificates (证书服务) → Code Signing (代码签名) (/ssl/codesigning) in the console to browse the full range. At the time of writing the following certificates are available; the page itself is authoritative:

BrandProductValidationTerm
CertumCode Signing OVOV1 / 2 / 3 years
CertumEV Code SigningEV1 / 2 / 3 years
DigiCertCode Signing, EV Code SigningOV / EV1 year

Certum code signing certificates are delivered on Certum's SimplySign cloud signing platform. The signing key is held in the CA's secure cloud hardware; after you authenticate in the SimplySign app you can sign on your own machine without managing a physical token. You need to provide a SimplySign account email when ordering.

Note

Under current industry rules, code signing private keys must be kept on compliant hardware or a cloud HSM and cannot be exported as ordinary files. That is why, unlike SSL certificates, there is no .key file to download for a code signing certificate.

OV or EV

OV code signingEV code signing
What is validatedThe organization's legal existence and contact detailsEverything in OV plus stricter checks such as jurisdiction, registration number and business category
Typical useGeneral desktop software, internal tools, scriptsSoftware where publisher identity matters most; some platform processes (for example certain driver publishing channels) require EV
Vetting timeUsually 1–3 business daysUsually 3–5 business days

Vetting times are set by the CA and the figures above are typical only. Complete information that can be verified in public records speeds things up.

What to prepare

Have the following ready before you order. Organization details must match your business registration or public records.

Basic information

  • SimplySign account email (Certum products)
  • A CSR (Certificate Signing Request)
  • Organization name, country, state/province and city

Additional information for EV

  • Business category: Private Organization, Government Entity, Business Entity or Non-Commercial Entity
  • Company registration number
  • Jurisdiction country, and jurisdiction state and city
  • Street address, postal code, tax ID and a phone number for verification

Administrative contact

  • First name, last name, email and phone. The CA may use this contact to verify the request.

Ordering

  1. Open Certificates → Code Signing and click Add to cart (加入购物车) on a product, or Buy now (立即购买) to go straight to the cart. Code signing certificates are a one-time purchase for the term shown on the product.
  2. Check out in the cart (/billing/cart). An invoice is created, and an order with status Pending appears under My Certificates.
  3. Pay the invoice under Billing → Invoices (/billing/invoices).
  4. After payment, contact us with the order ID and the information listed above, and we will help you submit the request to the CA.
  5. The CA vets your organization. Keep the administrative contact's email and phone reachable; the CA may ask for documents or call to verify.
  6. Once vetting is complete the certificate is issued and the order changes to Active. Certum certificates appear in your SimplySign account.

The platform syncs order status from the CA automatically at regular intervals, so you can follow progress under My Certificates.

Signing once the certificate is issued

With Certum SimplySign the usual workflow is:

  1. Install Certum's SimplySign client on the machine you sign from, sign in with your SimplySign account and complete authentication.
  2. While connected, the certificate appears in the system certificate store, where common signing tools can use it.
  3. Sign with a tool such as Windows signtool, adding a timestamp, for example:
powershell
signtool sign /n "Example Ltd" /fd sha256 /tr <RFC 3161 timestamp URL from your CA> /td sha256 app.exe
signtool verify /pa /v app.exe

Follow Certum's official SimplySign documentation for client installation and configuration details.

Tip

Always timestamp your signatures. A timestamped signature stays valid after the certificate expires; one without a timestamp becomes invalid when the certificate does.

Renewal and changes

Before a code signing certificate expires, buy a new one for the term you need. If your organization name or address changes, or you need the certificate revoked (for example if you suspect the account has been misused), contact us with the order ID.

Adakah halaman ini membantu?