Securing your website with SSL can help boost your search ranking. Here's how.
Starting this Wednesday, October 22, Gandi will begin issuing SHA-2 Standard, Pro and Business SSL certificates.
As you may have heard, the SHA-1 signature algorithm is being gradually deprecated in favor of SHA-2 (including SHA256, SHA-512, and so on).
Don't panic, though. At present, it's still really hard to break a SHA-1 hash. But collision attacks against SHA-1 will only become easier, so the sooner everyone migrates, the better.
Note that if you are currently using a SHA-1 certificate or want to buy one, you will still be able to do so. We are now entering a transition period where both the algorithms are supported. SHA-1 will be supported until 1 January 2017.
The majority of certification authorities, browsers, and operating systems already support SHA-2. You may encounter compatibility problems in some cases, for example with Mozilla Firefox, as not all root certificates supporting SHA-2 have been added. This process is now underway for various browsers.
If you're ready to migrate to SHA-2, you have two options to choose from:
- If you want to secure your website or application with SHA-2 only, and the issue of compatibility is not a concern, install your SHA-2-signed certificate along with the SHA-2 intermediate certificate only. This solution is the most secure, since the entire certificate chain will be SHA-2. It is a good option if you want to emphasize security over compatibility, or if you are certain that your visitors have SHA-2 enabled browsers (for example, all the employees of a company are using modern browsers to access a secure site).
- If you want to provide SHA-2 while avoiding compatibility issues with certain browsers that have not yet updated the root certificates, you can use the intermediate certificate with SHA-2 enabled and add the cross-signed SHA-1 intermediate certificate as well. If so, the last element of the chain of trust will be SHA-1, which is not optimally secure. This option is useful during the transition period: once all relevant browsers have performed the update, you can then remove the cross-signed intermediate certificate. This option is good if you want to switch to SHA-2 without disturbing visitors whose browsers do not have updated root certificates.
Attention! New intermediate certificates, which differ from those used with plain old SHA-1, will be issued with certificates signed with SHA-2. Be sure to use the correct intermediate certificate to match the hashing algorithm used in your main certificate. You can verify the signature of the certificate with the following command:
$ openssl x509 -in example.crt -text -noout
The output will contain lines like the following, indicating the certificate is signed with SHA-1 or SHA-2, respectively.
For certificates issued with SHA-1:
Issuer: C=FR, O=GANDI SAS, CN=Gandi Standard SSL CA
Signature Algorithm: sha1WithRSAEncryption
For certificates issued with SHA-2:
Issuer: C=FR, ST=Paris, L=Paris, O=Gandi, CN=Gandi Standard SSL CA 2
Signature Algorithm: sha256WithRSAEncryption
Here's an example of a valid trust chain for a SHA-2 certificate:
0 s:/OU=Domain Control Validated/OU=Gandi Standard SSL/CN=example.com
i:/C=FR/ST=Paris/L=Paris/O=Gandi/CN=Gandi Standard SSL CA 21 s:/C=FR/ST=Paris/L=Paris/O=Gandi/CN=Gandi Standard SSL CA 2
i:/C=US/ST=New Jersey/L=Jersey City/O=The USERTRUST Network/CN=USERTrust RSA Certification Authority2 s:/C=US/ST=New Jersey/L=Jersey City/O=The USERTRUST Network/CN=USERTrust RSA Certification Authority
i:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root
We have put in place some rules to ensure we deliver the right certificates for SHA-1 and SHA-2. Please be sure you review these and get the right certificates for your site or application:
Until 1 January 2016:
- Certificates with an expiration date after 1 January 2017 will be issued as SHA-2 only, even if the CSR was generated with SHA-1.
- Certificates with earlier expiration dates will be issued as SHA-1 if the CSR was generated with SHA-1
- Certificates with earlier expiration dates will be issued as SHA-2 if the CSR was generated with SHA-2
After January 1, 2016:
- All certificates will be issued in SHA-2, regardless of the hash specified in the CSR
Note that if you already have a certificate, you can regenerate it as SHA-2 by chosing the regenerate option and using a CSR signed with SHA-2. Remember to update the intermediate certificate on your server if you do this.
For more information, please visit our documentation:
 Several weeks ago, our SSL partner, Comodo, began issuing certificates in SHA-2 if the expiration date of the certificate was after January 1, 2017. This caused some confusion for customers whose issued certificates weren't signed with the signature algorithm they were expecting, and who therefore may have installed the wrong intermediate certificates, resulting in some confusion. We weren't able to update our documentation to reflect this in a timely manner, and for this we sincerely apologize. You will now find all the information you need to set up your SHA-2 certificates at the links above.
 You can install the root certificate manually by navigating to this URL in Firefox:
A major vulnerability in the OpenSSL cryptographic software library has just been published (CVE-2014-0160). If you have a Gandi SSL certificate, please read this post carefully before taking action.
This flaw has existed for some time, and there is a possibility that X509/SSL private keys have been compromised undetectably.
This flaw is present in OpenSSL from version 1.0.1 up to and including 1.0.1f, referred to as the "heartbleed" bug (heartbleed.com).
If your servers are using an affected version of OpenSSL (If you aren't sure if your server is affected, you can try a tool like this one, not provided or tested by Gandi):
- If you are using our SSL certificates on our PaaS platform (Simple Hosting) or via our web accelerator, you should know we fixed this vulnerability as soon as we were informed of it, and we will try to give further details about how your private keys could have been exposed by our platform.
- If you are using our IaaS infrastructure (Gandi Cloud VPS), or that of another hosting provider, and your servers are using an affected version* of OpenSSL, you need to:
- Patch the openSSL version on any server you own and operate yourself by installing security updates provided in your package manager. (For example, on Debian, ensure you're using the official debian-security repository, then run `apt-get update` and `apt-get install openssl`, then restart all services that use SSL.)
- Generate new private keys and certificates to restore security of your services (see below if you're using a Gandi SSL certificate).
- If you are using our SSL certificates, either on our infrastructure (on our PaaS/Simple Hosting instances) or on external services, then it is recommended that you regenerate a CSR and private key. Note: Do not revoke the certificate! Replaced certificates will be automatically revoked (see update below). If you revoke the certificate yourself, you will not be able to replace it afterwards, and you'll instead have to buy a new one.
Additional technical information is available in this GandiKitchen blog post.
========= Update 17 April 2014 =========
If you regenerated a Gandi SSL certificate between 8 and 17 April:
Many customers have regenerated their SSL certificates as a result of the Heartbleed bug. Until today, old certificates which were replaced with new, regenerated ones were not automatically revoked. Due to popular demand, we promised (here and here) to revoke the old certificates.
We sent an email this morning to users who have regenerated a Gandi SSL certificate between 8 and 17 April to notify you that your old certificates will be revoked in 24 hours. Your old certificate will be revoked on the morning of 18 April, Paris time (as early as 1am PST). If you have regenerated a certificate but have not yet installed it on your infrastructure, now is the time to do so!
If you intend to regenerate a Gandi SSL certificate in the future:
We have implemented automatic revocation, which means that from today forward, regenerated certificates will be automatically revoked 48 hours after the replacement certificate has been issued.
Simple hosting now lets you use SSL certificates!
We have made many improvements to our SSL certificate offer and added great new features.
Starting today (November 16th, 2010), we are dropping our prices for creation and renewals of Pro SSL certificates:
* "1 address" Pro SSL certificates drop to $65 (£43, or €34) excl. VAT under A rates
* "Multi-address (wildcard)" Pro SSL certificates drop to $340 (£237, or €265) excl. VAT under A rates
Please feel free to view our SSL comparison page, or our simulator, to help you choose the right certificate for you. As a reminder, with every domain creation or transfer at Gandi, you get the first year free on e standard SSL certificate.