Ceci est une ancienne révision du document !
Table des matières
Let's Encrypt
Let's Encrypt est un projet soutenu par Internet Security Research Group (ISRG). L'objectif est de permettre à tous et gratuitement de pouvoir mettre en place des certificats SSL pour sécuriser les connexions.
Configuration des certificats Let's Encrypt
J'ai configuré les certificats pour plusieurs noms de domaines et voici la procédure suivie, pour le domaine fictif “plouf.com”.
On commence par activer les backports (sous Stretch) afin de bénéficier de la version de certbot la plus récente.
# vim /etc/apt/sources.list #(...ajouter à la fin du fichier :) # Backports repository deb http://ftp.debian.org/debian stretch-backports main
Dans mon cas, après installation sans les backports, certbot était en version 0.10 alors qu'avec les backports, on a la version 0.19.0.
# apt-get -t stretch-backports install python-certbot-apache
# certbot --version
certbot 0.19.0
# certbot --apache Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator apache, Installer apache Which names would you like to activate HTTPS for? ------------------------------------------------------------------------------- 1: plouf.com 2: chat.plouf.com 3: wiki.plouf.com ------------------------------------------------------------------------------- Select the appropriate numbers separated by commas and/or spaces, or leave input blank to select all options shown (Enter 'c' to cancel): 1 Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for caliban.be Enabled Apache socache_shmcb module Enabled Apache ssl module Waiting for verification... Cleaning up challenges Created an SSL vhost at /etc/apache2/sites-available/caliban.be-le-ssl.conf Enabled Apache socache_shmcb module Enabled Apache ssl module Deploying Certificate for caliban.be to VirtualHost /etc/apache2/sites-available/caliban.be-le-ssl.conf Enabling available site: /etc/apache2/sites-available/caliban.be-le-ssl.conf Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access. ------------------------------------------------------------------------------- 1: No redirect - Make no further changes to the webserver configuration. 2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration. ------------------------------------------------------------------------------- Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 Redirecting vhost in /etc/apache2/sites-enabled/caliban.be.conf to ssl vhost in /etc/apache2/sites-available/plouf.com-le-ssl.conf ------------------------------------------------------------------------------- Congratulations! You have successfully enabled https://plouf.com You should test your configuration at: https://www.ssllabs.com/ssltest/analyze.html?d=plouf.com ------------------------------------------------------------------------------- IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/caliban.be-0001/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/caliban.be-0001/privkey.pem Your cert will expire on 2018-04-10. To obtain a new or tweaked version of this certificate in the future, simply run certbot again with the "certonly" option. To non-interactively renew *all* of your certificates, run "certbot renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le
On peut tester un renouvellement des certificats avec la commande suivante :
# certbot renew --dry-run
Actuellement, ça foire chez moi… Pas encore compris pourquoi.