The sys admin's daily grind – Let's Encrypt

Always at Hand

Article from Issue 187/2016
Author(s):

Columnist Charly fights the fight for free SSL certificates with Let's Encrypt. He particularly likes the matching software client that takes care of everything – from certificate retrieval to web server integration.

Although more and more web servers now use TLS, small businesses and amateur users are worried about the administrative overhead that accompanies SSL certificates. The Electronic Frontier Foundation, the University of Michigan, and the Mozilla foundation helped launch a project that addresses two pain points.

For one thing, it distributes Let's Encrypt [1] SSL certificates free of charge. For another – and this is where the project scores points compared with other free offerings – it delivers a Python client software tool that autonomously takes care of creating, validating, signing, and renewing certificates in good time. It even helps administrators integrate certificates with services running on their servers.

For Debian and its derivative distributions, you can pick up prebuilt packages. If you prefer to do it yourself – or are forced to do so – you can retrieve the Let's Encrypt client from GitHub with the following command:

git clone https://github.com/letsencrypt/letsencrypt

In the letsencrypt directory, you will now find a tool by the name of letsencrypt-auto. To use it to create a certificate for my example domain, <mydomain>.com, I would just type the following command:

sudo ./letsencrypt-auto certonly --standalone -d <mydomain>.com

Here certonly creates a certificate but does not automatically integrate it with the web server configuration. I prefer to do this myself; after all, this part of the software is still beta and only works correctly for Apache installations that have not had their configuration manipulated by admins.

The --standalone parameter starts a web server for validation purposes – this is one of the reasons the tool needs root privileges. Next, letsencrypt-auto briefly stops the active web server; the server is only allowed to continue doing whatever it was doing after passing the SSL checks.

Web Server Integration

The certificates generated here – cert.pem, chain.pem, and fullchain.pem, which combines the previous two, and the private key privkey.pem – end up in the /etc/letsencrypt/live/<mydomain>.com/ directory. To integrate this with an Apache web server, I need to pay attention to the Apache version number. Listing 1 shows the required instructions.

Listing 1

Integrating Certificates

 

To renew the certificates, which are only valid for 90 days (Figure 1), automatically, you can simply run letsencrypt-auto with the renew parameter within this period.

Figure 1: The browser reporting that the Let's Encrypt certificate is perfectly okay, but it expires May 30.

Charly Kühnast

Charly Kühnast is a Unix operating system administrator at the Data Center in Moers, Germany. His tasks include firewall and DMZ security and availability. He divides his leisure time into hot, wet, and eastern sectors, where he enjoys cooking, freshwater aquariums, and learning Japanese, respectively.

Infos

  1. Let's Encrypt: https://letsencrypt.org

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy Linux Magazine

SINGLE ISSUES
 
SUBSCRIPTIONS
 
TABLET & SMARTPHONE APPS
Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • The sys admin's daily grind: Let's Encrypt wildcards

    The pleasure of owning a nice domain like sensorenresidenz.de is clouded by the requirement of an X.509 certificate for every subdomain that the admin wants or has. Columnist Charly can help boost the webmaster's spirits.

  • Blog Central

    WordPress is one of the most popular content management systems. With the introduction of the new Gutenberg editor, now is the time to (re)learn WordPress.

comments powered by Disqus

Direct Download

Read full article as PDF:

Price $2.95

News