News for hackers. Stuff that matters.
Re:Let's Encrypt has issued its first million certificates by pingec on Tuesday March 08, 2016 @08:06AM (#11244941)
Do their certificates still expire in only 90 days? That makes them very unappealing to me :/

Edit: I understand and agree on why they made it like this. But automating it is not an option in my use case, oh well... I agree it's for the better in the grand scheme of things :).

Re:Let's Encrypt has issued its first million certificates by throwaway7767 on Tuesday March 08, 2016 @08:13AM (#11244971)
Yes.

I think they do that on purpose to get people to automate the certificate renewal. Their default client of course messes with all sorts of configuration to make auto-renew work "out of the box".

Many people (myself included) aren't fans of their client getting so much access, but there are other clients out there that don't need it. I use acme-tiny[0] in a small shell cronjob once a month. It lets acme-tiny request a renewed certificate. Then it checks that the new certificate is valid, copies it to the right places and reloads the relevant services.

Honestly, I couldn't be happier about not having to manually change certificates again.

[0] https://github.com/diafygi/acme-tiny

Re:Let's Encrypt has issued its first million certificates by Ao7bei3s on Tuesday March 08, 2016 @08:20AM (#11245003)
Stop spreading FUD: it does not "mess with all sorts of configuration".

_Renewal doesn't touch any config files at all._ "letsencrypt-auto" puts the certs/keys under /etc/letsencrypt/keys. On renewal, new files get added. Old files are never touched. /etc/letsencrypt/live contains symlinks to the most recent files. Your webserver config uses these => its config does not need to be changed for renewal.

What you're talking about is only the initial certificate installation with "letsencrypt-auto run", and it makes a very targeted change in your Apache config. Use etckeeper if you don't trust it. If you still don't want that, use "letsencrypt-auto certonly".

(Note on server restarts: It also supports multiple methods, one of which is the webroot method, with which letsencrypt-auto does the challenge by putting a file under .well-known/acme-challenge/ of your webroot and lets your webserver handle the request, so it doesn't need to restart/replace your webserver itself.)

And about all these "minimalistic tools": I've seen one that literally did "new-cert.sh > $cert-file". If it failed (e.g. due to ratelimit, no internet connectivity, ...), it would null your old cert! Written and used by very smug people.

Re:Let's Encrypt has issued its first million certificates by throwaway7767 on Tuesday March 08, 2016 @08:24AM (#11245018)
It wasn't intended to be FUD. The letsencrypt client needs to change the configuration of other services. This is a fact. Not everyone is happy about that, so I pointed out an alternative.

If you're happy with the official client, by all means, use it! There's nothing inherently wrong with that approach, it's just not compatible with the way I and some others prefer to do things.

EDIT in response to your edit:

> And about all these "minimalistic tools": I've seen one that literally did "new-cert.sh > $cert-file". If it failed (e.g. due to ratelimit, no internet connectivity, ...), it would null your old cert! Written and used by very smug people.

Absolutely, the minimal tools are not for people who don't know what they're doing. You absolutely would not run acme-tiny for example with write access to your actual cert that the web server is using, because any number of failure scenarios would result in downtime. That's why I specifically addressed that in the initial post you're replying to when I said: "Then it checks that the new certificate is valid, copies it to the right places and reloads the relevant services".

Re:Let's Encrypt has issued its first million certificates by detaro on Tuesday March 08, 2016 @09:15AM (#11245297)
> The letsencrypt client needs to change the configuration of other services. This is a fact. Not everyone is happy about that, so I pointed out an alternative.

No, it doesn't NEED to. It's the most commonly discussed option, but it is not necessary. It can do the exact same "write to a folder in the webroot" mode most of the alternatives use.

(I'm not saying that there is no reason to use an alternative client, but that's not it)

Re:Let's Encrypt has issued its first million certificates by nkuttler on Tuesday March 08, 2016 @08:33AM (#11245065)
The official letsencrypt client never touched any of my config files, it doesn't have to if you prefer to do it yourself.
Re:Let's Encrypt has issued its first million certificates by ceejayoz on Tuesday March 08, 2016 @08:44AM (#11245133)
> Stop spreading FUD: it does not "mess with all sorts of configuration".

It does more than you'd expect, IMO.

> letsencrypt-auto is a wrapper which installs some dependencies from your OS standard package repositories (e.g. using apt-get or yum), and for other dependencies it sets up a virtualized Python environment with packages downloaded from PyPI.

http://letsencrypt.readthedocs.org/en/latest/using.html

I was certainly a bit surprised when apt-get ran.

Re:Let's Encrypt has issued its first million certificates by Vespasian on Tuesday March 08, 2016 @10:09AM (#11245639)
As said by others if you run it with certonly it doesn't touch the config at all. My cronjob contains a

path/to/letsencrypt-auto certonly --webroot --renew-by-default -w /var/www/letsencrypt/ -d example.com

and puts the signed certificates into /etc/letsencrypt/live/excample.com/fullchain.pem . This is followed by a service nginx reload

I did not trust their automatic configuration as well so I simply configured nginx to use the keys + cert and to serve .well-known/acme from /var/www/letsencrypt/ for all my domains.

That's all. It works quite fine and if something does not work (e.g. python breaks.) such that the renewal is unsuccessful. LE will send you an email in advance (I think 30 days) so you have plenty of time to look after it.

Re:Let's Encrypt has issued its first million certificates by jpablo on Tuesday March 08, 2016 @10:07AM (#11245622)
I don't think its fud. Calling apt-get is just crazy on my view.
Re:Let's Encrypt has issued its first million certificates by mike-cardwell on Tuesday March 08, 2016 @08:20AM (#11245006)
I haven't fully automated mine yet, but I get alerts when any of my certs are getting close to expiry and I just have to run "/etc/letsencrypt/process.sh" now and it handles everything automatically at that point.

I'd rather run that script manually 4 times a year than go through the pain of renewing all of my certs by logging in to websites and pasting CSR's and Certs around every 1 or 2 years.

Once I'm comfortable with the process I'll just cron it and forget about it.

Re:Let's Encrypt has issued its first million certificates by feld on Tuesday March 08, 2016 @09:38AM (#11245448)
Don't forget this[1] gem which is my favorite way to use letsencrypt. It will let me run it by cron (or periodic on FreeBSD) plus I can have my own post-run script that takes my certificates and keys and puts them in the format I need for Hitch (SSL termination for Varnish), push those changes, restart the service _inside_ a FreeBSD jail automatically.

It's advanced setups like this where LetsEncrypt fails out of the box, but it's nice we have tools like this at our disposal now.

[1] https://github.com/lukas2511/letsencrypt.sh

Re:Let's Encrypt has issued its first million certificates by Ao7bei3s on Tuesday March 08, 2016 @08:09AM (#11244958)
You're supposed to automate renewal.

Since v0.4.0 all it takes is a "letsencrypt renew && apachectl graceful" in a daily cronjob (or, preferably, systemd timer), it handles the rest. Tweak as you like.

Re:Let's Encrypt has issued its first million certificates by jqueryin on Tuesday March 08, 2016 @08:18AM (#11244995)
Assuming you use Apache. For many, it's simply not a fast enough web server without reverse proxies in front of it.

Still crossing fingers for full nginx support soon.

Re:Let's Encrypt has issued its first million certificates by creshal on Tuesday March 08, 2016 @08:30AM (#11245050)
And, of course, there's other services than web servers that benefit from LE certificates. Mail, FTP, chat, etc. …
Re:Let's Encrypt has issued its first million certificates by Ao7bei3s on Tuesday March 08, 2016 @08:35AM (#11245075)
No, actually not.

"letsencrypt-auto renew" uses the same settings you've used with "letsencrypt-auto run/certonly". If you're using nginx, that's probably the --webroot method. Which works for renewals too.

Re:Let's Encrypt has issued its first million certificates by nkuttler on Tuesday March 08, 2016 @08:34AM (#11245074)
I don't know, I don't want letsencrypt to touch my config files. It just works fine without that "magic" anyway if you're willing to add a few lines to a config file.
Re:Let's Encrypt has issued its first million certificates by ptaffs on Tuesday March 08, 2016 @08:56AM (#11245197)
I agree, but i think the LE target audience is not you. Their whole thing is to be easy and use the "magic", to get the people who don't want to buy a certificate or deal with the config files, onto good encryption. I'm their audience and now my low-power volunteer run FM radio station website has HTTPS with a recognised CA.
Re:Let's Encrypt has issued its first million certificates by pde3 on Wednesday March 09, 2016 @08:42PM (#11256936)
If you use the letsencrypt python client with "certonly --webroot", it will never touch your config files at all. You can add "-n" to make everything non-interactive and command line-only.

If you use letsencrypt with "certonly --apache" (or --nginx, when the nginx plugin is released) it will make only transient changes to your config in order to obtain the cert, and then restore it to the original state before exiting.

If you use letsencrypt with "run" (which is the default command) it will make config changes if those appear to be necessary for installing the cert.

One challenge we've had is how to design the command line interface to ensure that the users who want maximum automation get it, and the users who want maximum manual control also get that. Both set of behaviour are available.

Re:Let's Encrypt has issued its first million certificates by ascorbic on Tuesday March 08, 2016 @09:36AM (#11245431)
Use webroot auth and it's fine with nginx. I just ran my first set of renewals with half a dozen domains on nginx. All fine apart from one which hadn't used webroot when I first set it up. Edited the config and it then worked fine.
Re:Let's Encrypt has issued its first million certificates by dingaling on Tuesday March 08, 2016 @10:45AM (#11245896)
Be sure to have a script that checks the results of your cronjobs, though:

"It is possible to hit the rate limit using letsencrypt renew and have it fail or partially fail for that reason."

https://community.letsencrypt.org/t/help-us-test-renewal-wit...

They launched with 90-day expiry but without a robust renewal process.

Re:Let's Encrypt has issued its first million certificates by Kadin on Tuesday March 08, 2016 @01:45PM (#11247458)
True. Although if you run it daily, you'll have multiple opportunities for the renewal to go through before it actually expires. It'll survive a couple of unsuccessful tries in the default/recommended configuration, at least if I'm understanding everything correctly.
Re:Let's Encrypt has issued its first million certificates by pingec on Tuesday March 08, 2016 @08:46AM (#11245142)
I understand and agree on why they made it like this. But automating it is not an option in my use case, oh well... I agree it's for the better in the grand scheme of things :).
Re:Let's Encrypt has issued its first million certificates by ris on Tuesday March 08, 2016 @02:52PM (#11247998)
Since v0.4.0 all it takes is a "letsencrypt renew && apachectl graceful" in a daily cronjob"

I'm glad your setup is so simple.

Re:Let's Encrypt has issued its first million certificates by ubergesundheit on Tuesday March 08, 2016 @10:05AM (#11245610)
May I point you to the awesome Caddy server of Matt Holt [0]. It automatically obtains and !renews! lets-encrypt certificates.

[0] https://github.com/mholt/caddy

Re:Let's Encrypt has issued its first million certificates by nly on Tuesday March 08, 2016 @08:52AM (#11245182)
Go get a free 3 year cert for up to 5 domains from WoSign then.

https://buy.wosign.com/free/

Re:Let's Encrypt has issued its first million certificates by warrenm on Tuesday March 08, 2016 @05:29PM (#11249321)
>"automating it is not an option in my use case"

Then you're doing it wrong - there is no reason you shouldn't be able to automate it that I can envision

Re:Let's Encrypt has issued its first million certificates by technion on Tuesday March 08, 2016 @09:30PM (#11250463)
There are valid scenarios. Placing a certificate on something like an F5 or Citrix VPX appliance pretty well forces you down the email verification route.

Then you've got those appliances that take a power cycle and 30 minute outage to install such a certificate. Five year certs are very attractive for this situation.

Re:Let's Encrypt has issued its first million certificates by kcbanner on Tuesday March 08, 2016 @08:59AM (#11245220)
Why?