DigiCert Blog

All posts under: Announcements

  1. New CAA Requirement: What You Should Know

    Things are heating up at the CA/Browser Forum with exciting proposals surrounding inclusion of the Wi-Fi Alliance (WFA) as a subjectAltName otherName, new validation methods, and debates over how the CAB Forum will continue operating. One of these new proposals is the recently passed Mozilla ballot that will require all Certificate Authorities (CAs) to check…


  2. OpenSSL Patches “HIGH” Security Vulnerability in 1.1.0

    Early this morning, the OpenSSL project team released the security patch 1.1.0e to fix a “HIGH” severity security vulnerability found in OpenSSL 1.1.0. Version 1.0.2 is not affected. However, system admins should patch their 1.1.0 OpenSSL framework immediately. This bug does not affect SSL/TLS certificates. No actions related to SSL/TLS certificate management are required. Encrypt-Then-Mac…


  3. Introducing the Standard User Role in CertCentral

    We wanted to let you know about a recent CertCentral updates, which includes a new Standard User role. Now when creating or editing Users in your account, this role is available by default for all CertCentral customers. About Standard Users The new Standard User is allowed to place requests for certificates, such as new orders,…


  4. OpenSSL Patches 3 Security Vulnerabilities in OpenSSL 1.1.0

    This morning, the OpenSSL project team released the security patch 1.1.0c for three security vulnerabilities discovered in OpenSSL 1.1.0. This patches fix one “high severity,” one “moderate severity,” and one “low severity” vulnerabilities. None of these bugs affect SSL/TLS certificates. No actions related to SSL/TLS certificate management are required. Source code for all the OpenSSL…


  5. Google CT to Expand to All Certificates Types

    A recent Google announcement says all publicly trusted SSL/TLS certificates issued in October 2017 or later will be expected to comply with Chrome’s Certificate Transparency (CT) policy in order to be trusted by that browser. Since January 2015, Chrome has required Extended Validation (EV) certificates to comply with CT, but now with this policy change, it…