Stephen McHenry, director of information security engineering at Google, said today in a post that Google will upgrade all of its SSL certs to the new length by the end of this year -- the first wave starting on Aug. 1. Google also will upgrade the root certificate that it uses to sign its SSL certificates to 2048-bit.
The Certificate Authority/Browser (CA/B) Forum has mandated that CAs upgrade their 1024-bit key RSA certs for SSL sites and code-signing by the end of this year. Several major vendors, including Symantec and Microsoft, have announced they are upgrading their SSL certs to the 2048-bit key length as part of an industry trend to ratchet up security for SSL. SSL has been under scrutiny in the past few years, as researchers have demonstrated various types of attacks and cracks of the protocol.
"I think pretty much everyone is moving to 2048 bits by the end of 2013, and that's likely the reason Google is," says Ivan Ristic, director of engineering at Qualys. "Microsoft, Microsoft, NIST, CA/B Forum -- they all require transition to 2048-bit keys by the end of the year. The CA/B forum is doing a great job with their Baseline Requirements."
[Amid growing concerns of threats to and the integrity of the certificate authority (CA) infrastructure, the world's biggest CAs have banded together to promote and evolve stronger website security. See Major Certificate Authorities Unite In The Name Of SSL Security.]
The National Institute of Standards (NIST) has recommended the discontinuation of 1024-bit certificates at the end of this year, and browser and CA members of the CA/Browser Forum have adopted NIST's guidelines here.
"Most client software won't have any problems with either of these changes, but we know that some configurations will require some extra steps to avoid complications. This is more often true of client software embedded in devices, such as certain types of phones, printers, set-top boxes, gaming consoles, and cameras," Google's McHenry said.
In order to avoid any problems for client software, Google recommends validating the certificate chain; including "a properly extensive" set of the root certificates; supporting Subject Alternative Names (SANs); and supporting the Server Name Indication (SNI) extension.
Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.