Google says the upgrade, which includes the root certificate that the company uses to sign all of its SSL certificates, will be completed “in the next few months.” Previously, however, Google was more specific and said it was aiming to finish the process by the end of 2013.
F**k it, we'll do it live!
Our biggest ever edition of TNW Conference is fast approaching! Join 10,000 tech leaders this May in Amsterdam.
Of course, Google also planned to start the process on August 1, but today (July 30) the company revealed it had “already started.” The decision to start early is likely a decision related to how much work there is ahead.
Google previously said some configurations will require extra steps to avoid complications. The company specifically mentioned client software embedded in devices such as some phones, printers, set-top boxes, gaming consoles, and cameras.
Client software that makes SSL connections to Google (usually in the form of HTTPS) thus must adhere to the following requirements:
- Perform normal validation of the certificate chain.
- Include a properly extensive set of root certificates contained.
- Support Subject Alternative Names (SANs).
For the second point, Google offers an example set in its FAQ which should be sufficient. The company also notes clients should, but are not required to, support the Server Name Indication (SNI) extension as they may need to make an extra API call to set the hostname on an SSL connection.
Most users and businesses will not be affected by this whole process. If you think you will be, however, you’ll want to read over the more technical details in this document: How to Use X.509 Certificates and SSL For Secure Communications.
Top Image Credit: Kimihiro Hoshino/Getty Images