Sample Category

This article provides step-by-step instructions in identifying key generation method.

This article provides step-by-step instructions for ACME Service Configuration and Certificate Issuance via HTTP Validation with Certbot

The Certificate Authority (CA) industry was alerted of compliance implications related to the inclusion of a specific extension (OCSP-signing extended key usage) in CA certificates which has, under certain conditions, unintended compliance and security implications. A number of GlobalSign Issuing CAs have been impacted by this issue. While no key compromise or security incident has taken place, we will be revoking these Issuing CA’s as part of our remediation plans in accordance with the CA/B Forum Baseline Requirements and the GlobalSign CPS. Revoked intermediate certificates can cause errors in the validation of certificates signed by these intermediate certificates.

Renewing a certificate is the process of replacing a certificate (preferably) before it expires. A user takes an existing certificate and requests a new one using a different CSR (key pair) from the original, most other fields will be the same (see list of fields below). This functionality will be available for certificates that have been issued through either the Atlas portal, Atlas APIs, or ACME. The implementation of this new feature is focused on the Atlas portal.

The CA and Browser Forum’s has new BR guidelines that affect code signing certificates. Private Keys and Code Signing Certificates needs to be stored on a Cloud HSM, Physical HSM, or security token. The token or HSM must be compliant with FIPS 140 Level 2 or 3. After these new guidelines, conventional way of signing builds using a PFX file is obsolete, and developers are facing issues related to Signing executables. This article will help you in Signing Windows Executables using GlobalSign’s Code Signing Certificate, Azure Key Vault and Azure SignTool.