Why is this important? If you were to revoke your certificate, like I had to after the HeartBeat bug, you can tell web browsers that the certificate authority has your certificate revoked and they can verify that using the CA signature.
Now while it is not currently possible to require that this is provided for your website, like how you can set HTTP Strict Transport to tell the browser you require that your site is secure, it is important to start implementing it now so when such a flag exists, we could just add that flag and immediately prevent any server that doesn’t do stapling from faking our site.
I have updated my guide on implementing SSL properly on Nginx at https://plus.google.com/104359338500189725198/posts/iToJf8FgBSu
If you don’t want to re-read, just add these lines to your config.
ssl_trusted_certificate /sub.class2.server.ca.pem;#Your SSL provider’s certificate with OCSP.
resolver 22.214.171.124 126.96.36.199 valid=300s;
Note: I had to upgrade to Nginx 1.6 in-order to get stapling to work.
You can test the configuration in 2 ways. SSL Labs shows if stapling is enabled and the following OpenSSL command will show if it’s enabled.
openssl s_client -connect mrgeckosmedia.com:443 -tls1 -tlsextdebug -status
If it shows something like the following, then you are fine.
OCSP Response Data:
OCSP Response Status: successful (0x0)
If you get the following, your server isn’t configured properly or your certificate authority doesn’t have an OCSP server.
OCSP response: no response sent