server-configs-nginx/h5bp/directive-only/ssl.conf

# Protect against the BEAST attack by not using SSLv3 at all. If you need to support older browsers (IE6) you may need to add
# SSLv3 to the list of protocols below.
ssl_protocols              TLSv1 TLSv1.1 TLSv1.2;

# Ciphers set to best allow protection from Beast, while providing forwarding secrecy, as defined by Mozilla - https://wiki.mozilla.org/Security/Server_Side_TLS#Nginx
ssl_ciphers                ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:ECDHE-RSA-RC4-SHA:ECDHE-ECDSA-RC4-SHA:AES128:AES256:RC4-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK;
ssl_prefer_server_ciphers  on;

# Optimize SSL by caching session parameters for 10 minutes. This cuts down on the number of expensive SSL handshakes.
# The handshake is the most CPU-intensive operation, and by default it is re-negotiated on every new/parallel connection.
# By enabling a cache (of type "shared between all Nginx workers"), we tell the client to re-use the already negotiated state.
# Further optimization can be achieved by raising keepalive_timeout, but that shouldn't be done unless you serve primarily HTTPS.
ssl_session_cache    shared:SSL:10m; # a 1mb cache can hold about 4000 sessions, so we can hold 40000 sessions
ssl_session_timeout  24h;

# SSL buffer size was added in 1.5.9
#ssl_buffer_size      1400; # 1400 bytes to fit in one MTU

# Session tickets appeared in version 1.5.9
#
# nginx does not auto-rotate session ticket keys: only a HUP / restart will do so and
# when a restart is performed the previous key is lost, which resets all previous
# sessions. The fix for this is to setup a manual rotation mechanism:
# http://trac.nginx.org/nginx/changeset/1356a3b9692441e163b4e78be4e9f5a46c7479e9/nginx
#
# Note that you'll have to define and rotate the keys securely by yourself. In absence
# of such infrastructure, consider turning off session tickets:
#ssl_session_tickets off;

# Use a higher keepalive timeout to reduce the need for repeated handshakes
keepalive_timeout 300; # up from 75 secs default

# remember the certificate for a year and automatically connect to HTTPS
add_header Strict-Transport-Security max-age=31536000;

# This default SSL certificate will be served whenever the client lacks support for SNI (Server Name Indication).
# Make it a symlink to the most important certificate you have, so that users of IE 8 and below on WinXP can see your main site without SSL errors.
#ssl_certificate      /etc/nginx/default_ssl.crt;
#ssl_certificate_key  /etc/nginx/default_ssl.key;
remove SSLv3 from the ssl protocol list As suggested in #44, and since h5bp doesn't support IE6 it seems to be appropriate to remove a protocol which is in the list only to permit use with IE6. 2014-07-28 16:16:09 +02:00			`# Protect against the BEAST attack by not using SSLv3 at all. If you need to support older browsers (IE6) you may need to add`
			`# SSLv3 to the list of protocols below.`
			`ssl_protocols TLSv1 TLSv1.1 TLSv1.2;`

move ssl config to a seperate file 2014-07-28 16:08:19 +02:00			`# Ciphers set to best allow protection from Beast, while providing forwarding secrecy, as defined by Mozilla - https://wiki.mozilla.org/Security/Server_Side_TLS#Nginx`
			ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:ECDHE-RSA-RC4-SHA:ECDHE-ECDSA-RC4-SHA:AES128:AES256:RC4-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK;
			`ssl_prefer_server_ciphers on;`

			`# Optimize SSL by caching session parameters for 10 minutes. This cuts down on the number of expensive SSL handshakes.`
			`# The handshake is the most CPU-intensive operation, and by default it is re-negotiated on every new/parallel connection.`
			`# By enabling a cache (of type "shared between all Nginx workers"), we tell the client to re-use the already negotiated state.`
			`# Further optimization can be achieved by raising keepalive_timeout, but that shouldn't be done unless you serve primarily HTTPS.`
			`ssl_session_cache shared:SSL:10m; # a 1mb cache can hold about 4000 sessions, so we can hold 40000 sessions`
use a much longer ssl_session_timeout To match the settiongs from istlsfastyet.com Add a mention of ssl_buffer_size even though it can 't be enabled yet 2014-07-28 16:54:31 +02:00			`ssl_session_timeout 24h;`

			`# SSL buffer size was added in 1.5.9`
			`#ssl_buffer_size 1400; # 1400 bytes to fit in one MTU`
move ssl config to a seperate file 2014-07-28 16:08:19 +02:00
disable ssl_session_tickets it's only recently added so is a config error otherwise 2014-07-28 16:42:35 +02:00			`# Session tickets appeared in version 1.5.9`
			`#`
turn off ssl session tickets Stolen from istlsfastyet.com's config It is probably a more logical default to turn off session tickets given the diff linked in the comment block. 2014-07-28 16:20:58 +02:00			`# nginx does not auto-rotate session ticket keys: only a HUP / restart will do so and`
			`# when a restart is performed the previous key is lost, which resets all previous`
			`# sessions. The fix for this is to setup a manual rotation mechanism:`
			`# http://trac.nginx.org/nginx/changeset/1356a3b9692441e163b4e78be4e9f5a46c7479e9/nginx`
			`#`
			`# Note that you'll have to define and rotate the keys securely by yourself. In absence`
			`# of such infrastructure, consider turning off session tickets:`
disable ssl_session_tickets it's only recently added so is a config error otherwise 2014-07-28 16:42:35 +02:00			`#ssl_session_tickets off;`
turn off ssl session tickets Stolen from istlsfastyet.com's config It is probably a more logical default to turn off session tickets given the diff linked in the comment block. 2014-07-28 16:20:58 +02:00
add increased ssl timeout 2014-07-28 16:29:04 +02:00			`# Use a higher keepalive timeout to reduce the need for repeated handshakes`
			`keepalive_timeout 300; # up from 75 secs default`

Default to use HTTP strict transport security 2014-07-28 16:30:00 +02:00			`# remember the certificate for a year and automatically connect to HTTPS`
Removed "includeSubDomains" As a best practice, Nginx should only direct clients to use the certificate on specified domains. This is because not all servers using other subdomains necessarily listen on 443 and because, unless it is a wildcard certificate, it likely won't be valid on subdomains other than WWW. 2014-10-14 06:16:22 +02:00			`add_header Strict-Transport-Security max-age=31536000;`
Default to use HTTP strict transport security 2014-07-28 16:30:00 +02:00
move ssl config to a seperate file 2014-07-28 16:08:19 +02:00			`# This default SSL certificate will be served whenever the client lacks support for SNI (Server Name Indication).`
			`# Make it a symlink to the most important certificate you have, so that users of IE 8 and below on WinXP can see your main site without SSL errors.`
			`#ssl_certificate /etc/nginx/default_ssl.crt;`
			`#ssl_certificate_key /etc/nginx/default_ssl.key;`