Skip to content
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

Should we give SSL sessions in Nginx a 1 day timeout? #6903

Closed
bmw opened this issue Apr 2, 2019 · 1 comment
Closed

Should we give SSL sessions in Nginx a 1 day timeout? #6903

bmw opened this issue Apr 2, 2019 · 1 comment

Comments

@bmw
Copy link
Member

bmw commented Apr 2, 2019

Inspired by https://jhalderm.com/pub/papers/forward-secrecy-imc16.pdf, we might want to look into changing our nginx plugin's behavior around TLS sessions. The Mozilla site where we get our TLS config from has the TLS session timeout a 1 day which is much longer than nginx's default of 5 minutes.

This behavior is not necessarily wrong, but it's making a tradeoff for performance over security and more in the favor of performance than is recommended in the paper linked above.

The purpose of this issue is to track looking into this. Why does Mozilla have this recommendation? Do we agree? If so, we can close this issue, but if not, we should update our configuration file at https://github.com/certbot/certbot/blob/master/certbot-nginx/certbot_nginx/options-ssl-nginx.conf.

@sydneyli
Copy link
Contributor

It was recommended to improve performance afaict. There still seems to be some disagreement about it as per mozilla/server-side-tls#198.

For this and other reasons outlined in the paper you linked and others I don't feel comfortable following this particular guideline. I'll also comment upstream!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants