Harden your SSL Security - The site is using outdated security.

def test
  puts hello world

If you’ve seen the following warning on your browser when accessing your already
configured nginx SSL, you probably need to work on getting it compliant.

There’s a couple of reasons why you’re getting the error and it may not be
apparent what exactly is the cause.

This article should help you get a A-grade in SSLLabs’s SSL Testing


As of 26 September 2014, Chrome (and also Firefox) have started the process to
sunset SHA1 certification
and will give the above error if you’re using
a certificate that is signed with SHA1.

If you’ve just installed a newly issued SSL cert from your certification
authority, you should be already be issued with a signed certificate in SHA-256
as most CA have already stopped signing them with SHA1.

If not, make sure you’ve request for a reissue of your certification with

###Disable Support for SSLv3

In your server block configuration on NGINX, specifically allow for non-v3
SSL protocol.

server {
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;


###Run a Logjam Test

Using the free Diffie-Hellman Server Test,
check if your site is vulnerable to poor encryption. If you are you’ll need to
generate a unique DH group to help beef it up.

Create a new DH Group Key

$ openssl dhparam -out dhparams.pem 2048

You should store this key in the same directory as your site’s existing certs.

Allow only certain Cipher Suites

# in your nginx configuration
  server {

    ssl_prefer_server_ciphers on;

Add your dhparam key into your configuration

server {
    ssl_prefer_server_ciphers on;
    ssl_dhparam /path/to/your/dhparams.pem;

Now, restart your NGINX are run the SSLLabs test

I hope this article can give you a quick hardening tip and should be part of
any new https deployment.