-
Notifications
You must be signed in to change notification settings - Fork 3k
Nginx SSL TLS and Cipher options #951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Please, I need to add this for my alexa MP3 playing to work... I don't know how to add that.
|
Any progress on this important part? |
Issue is now considered stale. If you want to keep it open, please comment 👍 |
Dead? |
Issue is now considered stale. If you want to keep it open, please comment 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently the Nginx options for TLS settings and ciphers are either fixed (ciphers) or modifiable only partially (TLS server templates for hosts allowing changes for HSTS and HTTP/2). More options would allow to use Mozilla Modern TLS 1.3 configurations or allow users to switch between old/intermediate/modern configurations and/or their individual options to suit their server/client needs and capability.
Describe the solution you'd like
/etc/nginx/conf.d/include/ssl-ciphers.conf
allowing to choosessl_protocols
(TLSv1.3),ssl_ciphers
(lists),ssl_prefer_server_ciphers
(off),ssl_ecdh_curve
(X25519:prime256v1:secp384r1)site.conf
files with more options to choose from, that would incorporate the above cipher options - again as per Mozilla recommendations above, potentially also with addition of OCSP stapling (probably separate subject due to complexity).Describe alternatives you've considered
Just editing of
/etc/nginx/conf.d/include/ssl-ciphers.conf
Additional context
Again, ideally both selectable individual options above and composite options to choose between old, intermediate and modern configurations as per Mozilla specs would be amazing.
As always - thank you for your great effort so far. No pressure and thank you for consideration.
The text was updated successfully, but these errors were encountered: