Re:Let’s Encrypt client will transition to a new name and a ...
by mholt on Wednesday March 09, 2016 @06:50PM
(#11256504)
Thank you for your kind remarks. :) It goes a long way to keeping the burnout away.
Re:Let’s Encrypt client will transition to a new name and a ...
by xt on Wednesday March 09, 2016 @06:39PM
(#11256459)
I've been working on a script that does this within Nginx. See https://github.com/torhve/lua-resty-letsencrypt
It's not quite production ready but it shows you it's technically possible
By default, all that's needed is to turn on ssl and you'll be up and running - including a let's encrypt certificate.
Following this vision is why I believe that let's encrypt limited the validity period of their certs (in addition to some security benefits and much lower OCSP load): Once the integration into clients has proceeded to this level where caddy is showing us it's going to, then even quicker expirations would become feasible - heck even as low as a week or so.
So, while I'm not planning on using caddy any time soon (I don't see a benefit to switching away from nginx right now), I applaud caddy for showing everyone how this should be done.
A huge thank you to the author. This goes to show how very important UX is even for backend-y stuff.