benqzq
October 27, 2017, 6:08pm
#1
I create certifications this way:
certbot --nginx -d domain.tld -d www.domain.tld
I then have to change manually (or run a sed operation) to change from:
listen 443 ssl; # managed by Certbot
To
listen 443 ssl http2; # managed by Certbot
Is there a chance you guys will add a parameter for adding http2 after ssl, directly in Certbot execution?
schoen
October 27, 2017, 6:10pm
#2
@erica , could you please opine on this feature request?
ahaw021
October 27, 2017, 6:51pm
#3
might a better way to do this is to have a template file?
That way the NGINX/Apache installer would read that.
i noticed that the ssl parameters come from a conf file but the other stuff is hard coded
# This file contains important security parameters. If you modify this file
# manually, Certbot will be unable to automatically provide future security
# updates. Instead, Certbot will print and log an error message with a path to
# the up-to-date file that you will need to refer to when manually updating
# this file.
ssl_session_cache shared:le_nginx_SSL:1m;
ssl_session_timeout 1440m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
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";
enable
Andrei
erica
October 27, 2017, 7:46pm
#4
It’s on our radar to support this in the future: https://github.com/certbot/certbot/issues/3646
For now, you could keep running that command, and even put it in a post hook: https://certbot.eff.org/docs/using.html#pre-and-post-validation-hooks
Or, you could manually manage your ssl options – if there’s already a listen 443 ssl http2 line in the config, we won’t overwrite it with listen 443 ssl;, but we also won’t add an include linking to certbot/certbot-nginx/certbot_nginx/options-ssl-nginx.conf.
2 Likes
system
November 26, 2017, 7:47pm
#5
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.