Securing Nginx or Tengine with OpenSSL
This guide assumes you already have your Webserver, Package:Tengine or Package:Nginx installed and serving pages on the standard HTTP port. You should also have the Package:OpenSSL installed and an SSL certificate and key file (either self signed or provided by a commercial supplier). If you need a certificate, you can get one free from . These guys will step you through the process of getting the certificate by following the instructions on their site. Follow the installation instructions here.
Put all your SSL configuration into a single file so that you can update it as security issues arise. This way, if you have multiple sites, they can all include the same file and you don't need to try and maintain the information for each site separately.
#- Not sure if both lines needed, but it works listen [::]:443 ssl; listen 443 ssl; #- Support current SSL standards and options only ssl_session_cache shared:SSL:10m; ssl_session_timeout 10m; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH"; ssl_session_tickets off; ssl_stapling on; ssl_stapling_verify on; #- And some security related headers add_header Strict-Transport-Security "max-age=63072000; includeSubdomains; preload"; #add_header X-Frame-Options DENY; add_header X-Content-Type-Options nosniff;
Comment out the Strict-Transport-Security if you want to have part of your site as non-SSL. Not recommended! X-Frame-Options is to deny the use of frames, which is good for security, but you'll find much of existing software still need frames.
Attach Certs To Your Site
Go to your /etc/tengine/sites-available/ directory and add the following to your first SSL site.
include /etc/tengine/ssl.conf; ssl_dhparam /etc/ssl/tengine/dhparam4096; ssl_trusted_certificate /etc/ssl/tengine/startssl_trust_chain.crt; ssl_certificate /etc/ssl/tengine/ssl-unified.crt; ssl_certificate_key /etc/ssl/tengine/ssl.key;
If you purchased a certificate that works for multiple domains, then these can be the same files for all your sites and you can place those lines in the above ssl.conf. In most cases, you will likely have different ssl certificates for different sites and you will likely want to name the files accordingly.
Building SSL Files
There are 4 files here for SSL in addition to the ssl.conf file you just included. Follow these steps to create them:
First, you should have a certificate file (ssl.crt in the example), and a key for that file (private_ssl.key). The header will determine which is which if you named them funny. Filenames aren't important. Open the file with vi and look for the text at the top between '-----' symbols, starting with BEGIN. If you use less, you won't see the header as less will attempt to decode the certificate to show you in the information in it.
- CERTFICATE This is a certificate
- RSA PRIVATE KEY This is your key!
If your KEY has a line that says ENCRYPTED, it is password protected. Since you probably don't want to issue a password every time you start your server, decrypt it with this command. You will need the password you used to encrypt the key. If your key does not say ENCRYPTED, you can probably just skip this step.
openssl rsa -in private_ssl.key -out /etc/ssl/tengine/ssl.key
That's the first file. The rest are even easier.
You want to create a chain of certificates that validate from you back to the root certificates installed in the browser. You may want to check with your SSL certificate provider. For StartSSL, you download their cert and attach it to your file:
Now make the unified certificate chain you need by combining your certificate and theirs.
cat ssl.crt sub.class1.server.sha2.ca.pem > /etc/ssl/tengine/ssl-unified.crt cp sub.class1.server.sha2.ca.pem /etc/ssl/tengine/startssl_trust_chain.crt
You use DH key parameters to exchange keys securely. Create this file with the following command:
openssl dhparam -out /etc/ssl/tengine/dhparam4096 4096
4096 might be overkill, but 1024 is the minimum and you might as well go all out just in case 1024 gets broken next month!
Be sure all these files are secure!
chmod 0600 /etc/ssl/tengine/*
Delete originals, clean up, then restart tengine. Repeat the above for each SSL site, giving descriptive names to your certificates and keys.
If you followed the above instructions, you should now have a secure site. Test it! on the SSL Labs Test Site. You should get an A+ rating. If you don't, go back and see if you missed anything, using the information from the test report to see what you need to check.