News for hackers. Stuff that matters.
Re:Chrome 68 will mark all HTTP sites as “not secure” by kelnos on Thursday February 08, 2018 @09:40PM (#16337499)
I have nginx fronting around 15 different (very low traffic) websites (most static, a few python), all of which have Let's Encrypt certs. The required additions to the nginx conf were minimal and easy. Adding a new subdomain is trivial. Fetching the initial certificate from Let's Encrypt is a short, easy command line. And "sudo certbot renew; sudo /etc/init.d/nginx reload" in a cron job keeps the certs up to date (the "renew" command is smart enough to go through the list of certs you have and renew them all).

It's really hard to imagine it getting much easier.

Re:Chrome 68 will mark all HTTP sites as “not secure” by andrewaylett on Friday February 09, 2018 @06:10AM (#16339365)
Try `certbot renew --post-hook "/etc/init.d/nginx reload`, which will only reload nginx if at least one certificate changed :).