[Google just announced][1] they will not be enforcing certificate transparency (CT) logging for all new TLS certificates until April 2018. In a previous [blog post][2], we advis…
PKI Consortium blog
Posts by tag Google
Looking Back at 2016 Fortunately, 2016 was not a year full of SSL/TLS vulnerabilities. Although some researchers did prove old cryptography algorithms should be put out to pastu…
The four letters, “http”, are known to technical and non technical users alike as the beginning of any web address. These have been ubiquitous for many years. But things are abo…
The policy change goes into effect October 2017 A recent Google announcement stated that all publicly trusted SSL/TLS certificates issued in October 2017 or later will be expect…
Google
I wrote about the [next version of the HTTP protocol][1] 18 months ago. Since then, HTTP/2 has gained significant traction, but not without generating some controversy along the…
OpenSSL
There is no doubt that content owners and publishers have a duty to encourage trust and the confidence during internet usage by adopting security best practices. If a customer b…
Always On SSL should be deployed to prevent the “Not secure” warning Website owners who do not secure their website with an SSL/TLS certificate will have to rethink their online…
Google is making [security icon changes][1] in the Chrome status bar. The changes are based on a [research paper][2] prepared by members of Google and University of California, …
Over the past several years there has been increased discussion about deprecating HTTP and making HTTPS the default protocol for the World Wide Web. (HTTP stands for “HyperText …
On January 1, 2016, the public trust certification authorities (CAs) will stop issuing SHA 1 signed SSL/TLS certificates. What will happen? Will all websites using SHA 1 fail? N…
