Last active
February 17, 2017 22:50
-
-
Save Yinchie/9dbee851dbde17dd74de9c37373950a6 to your computer and use it in GitHub Desktop.
My Ghost blog, NGiNX TLS configuration | X25519 & secp384r1 | RSA & ECDSA
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# RSA certificate | |
ssl_certificate /path/rsa_fullchain.pem; | |
ssl_certificate_key /path/rsa-2048.key; | |
# ECDSA certificate | |
ssl_certificate /path/ec_fullchain.pem; | |
ssl_certificate_key /path/ec-secp384r1.key; | |
# DH (Diffie–Hellman) | |
ssl_dhparam /path/dhparam4096.pem; | |
ssl_buffer_size 1400; | |
ssl_session_timeout 1d; | |
ssl_session_cache shared:SSL:50m; | |
ssl_session_tickets off; | |
# Modern configuration. | |
ssl_protocols TLSv1 TLSv1.1 TLSv1.2; | |
ssl_ciphers "ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS"; | |
ssl_prefer_server_ciphers on; | |
ssl_ecdh_curve X25519:secp384r1; | |
# OCSP Stapling. | |
# fetch OCSP records from URL in ssl_certificate and cache them. | |
ssl_stapling on; | |
ssl_stapling_verify on; | |
## verify chain of trust of OCSP response using Root CA and Intermediate certs | |
ssl_trusted_certificate /path/ec_fullchain.pem; | |
resolver 8.8.8.8 8.8.4.4 valid=300s; | |
resolver_timeout 5s; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment