News for hackers. Stuff that matters.
Re:Let’s Encrypt client will transition to a new name and a ... by heavenlyhash on Wednesday March 09, 2016 @01:31PM (#11254730)
Anyone looking to use Let's Encrypt and free to make choices regarding their server may want to check out https://caddyserver.com/ -- it has Let's Encrypt support baked right in.
Re:Let’s Encrypt client will transition to a new name and a ... by pilif on Wednesday March 09, 2016 @04:22PM (#11255811)
I've said it before when caddy was last mentioned, but this is how I want Let's Encrypt to work with all web servers. Yes. That includes the big ones like nginx, apache and even IIS.

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.

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

Re:Let’s Encrypt client will transition to a new name and a ... by geostyx on Wednesday March 09, 2016 @03:28PM (#11255519)
Caddy is working really well for me. Way easier than nginx to setup, and TLS is on by default.
Re:Let’s Encrypt client will transition to a new name and a ... by recursive on Wednesday March 09, 2016 @03:37PM (#11255572)
Wow, this is awesome. I had been assuming letsencrypt supported only Unixy operating systems. Most of the web hosts I care about necessarily run Windows, so I thought letsencrypt was out of reach. I wonder how they did this.
Re:Let’s Encrypt client will transition to a new name and a ... by simoncion on Wednesday March 09, 2016 @03:42PM (#11255607)
> I wonder how they did this.

The ACME protocol is simple and fully documented: https://letsencrypt.github.io/acme-spec/

Re:Let’s Encrypt client will transition to a new name and a ... by hackerboos on Wednesday March 09, 2016 @04:46PM (#11255957)
Dokku's Letsencrypt plugin is also very simple to use.

https://github.com/dokku/dokku-letsencrypt

Re:Let’s Encrypt client will transition to a new name and a ... by embik on Thursday March 10, 2016 @04:07AM (#11258073)
Caddy sounds great but I'm a bit worried by the fact it does not offer repositories for major Linux distributions. Shouldn't a component that important for public facing servers be included in standard software updating processes?
Re:Let’s Encrypt client will transition to a new name and a ... by nitrogen on Thursday March 10, 2016 @05:45AM (#11258398)
In my experience it's not typical for web infrastructure to come from distro packages, unfortunately.