Moving To "Let's Encrypt" TLS CertificatePublish date: Aug 20, 2016
As a fan of the EFF, and security in general, I was pretty excited to hear about the Let’s Encrypt project. Let’s Encrypt is a project sponsored by EFF, University of Michigan, Mozilla, Cisco and Akamai to provide free, signed TLS certificates. While I’ve used StartSSL in the past for free certificates, I’ve found their process a bit cumbersome (although in all fairness, they have done a ton of redesign this year). Despite the redesign, I went forward with using Let’s Encrypt to renew my TLS certificate.
I used the EFF Certbot as my client, which works fairly well, even on an older CentOS system. It couldn’t quite parse the Apache configuration correctly, but pointing to the certificate manually was not a difficult configuration change. In case anyone finds the configuration handy, here are the appropriate lines from my httpd.conf below.
Hopefully this begins an exciting new chapter in secure Internet communication and makes encrypted web communication the default, as it should be.
<VirtualHost x.x.x.x:443> SSLEngine on # Moving to let's encrypt SSLCertificateFile /etc/letsencrypt/live/<domain>/cert.pem SSLCertificateKeyFile /etc/letsencrypt/live/<domain>/privkey.pem SSLCertificateChainFile /etc/letsencrypt/live/<domain>/fullchain.pem ... </VirtualHost>