Alan Orth
a34cb1e666
The certbot-auto client that I've been using for a long time is now only supported if you install it using snap. I don't use snap on my systems so I decided to switch to the acme.sh client, which is imp- lemented in POSIX shell with no dependencies. One bonus of this is that I can start using ECC certificates. This also configures the .well-known directory so we can use webroot when installing and renewing certificates. I have yet to understand how the renewal works with regards to webroot, though. I may have to update the systemd timers to point to /var/lib/letsencrypt/.well-known.
56 lines
2.4 KiB
Django/Jinja
56 lines
2.4 KiB
Django/Jinja
{# helper variables and per-site defaults that we can't set in role defaults #}
|
|
{% set domain_name = item.domain_name %}
|
|
{# assume HSTS is off unless a vhost explicitly sets it to True #}
|
|
{% set enable_hsts = item.enable_hsts | default(False) %}
|
|
|
|
{# first, check if the current vhost has a custom cert (perhaps self-signed) #}
|
|
{% if item.tls_certificate_path is defined and item.tls_key_path is defined %}
|
|
|
|
# concatenated key + cert
|
|
# See: http://nginx.org/en/docs/http/configuring_https_servers.html
|
|
ssl_certificate {{ item.tls_certificate_path }};
|
|
ssl_certificate_key {{ item.tls_key_path }};
|
|
|
|
{# otherwise, assume host is using letsencrypt #}
|
|
{% else %}
|
|
|
|
# concatenated key + cert
|
|
# See: http://nginx.org/en/docs/http/configuring_https_servers.html
|
|
ssl_certificate {{ letsencrypt_root }}/certs/{{ domain_name }}.fullchain.pem;
|
|
ssl_certificate_key {{ letsencrypt_root }}/private/{{ domain_name }}.key.pem;
|
|
|
|
{% endif %}
|
|
|
|
ssl_session_timeout {{ nginx_ssl_session_timeout }};
|
|
ssl_session_cache {{ nginx_ssl_session_cache }};
|
|
ssl_buffer_size {{ nginx_ssl_buffer_size }};
|
|
|
|
ssl_dhparam {{ nginx_ssl_dhparam }};
|
|
ssl_protocols {{ nginx_ssl_protocols }};
|
|
ssl_ciphers "{{ tls_cipher_suite }}";
|
|
ssl_prefer_server_ciphers on;
|
|
|
|
{# OSCP stapling only works with real certs #}
|
|
{% if use_letsencrypt == True or item.tls_certificate_path %}
|
|
# OCSP stapling...
|
|
ssl_stapling on;
|
|
ssl_stapling_verify on;
|
|
resolver {{ nginx_ssl_stapling_resolver }};
|
|
{% endif %} {# end: use_letsencrypt #}
|
|
|
|
# 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;
|
|
|
|
{% if enable_hsts == True %}
|
|
# Enable this if you want HSTS (recommended, but be careful)
|
|
# Include all subdomains and indicate to Google that we want this pre-loaded in Chrome's HSTS store
|
|
# See: https://hstspreload.appspot.com/
|
|
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload" always;
|
|
{% endif %}
|