Live data from Hacker News

Let’s encrypt automation on Debian

eblog.damia.net

21–30 of 32 posts

Re: Let’s encrypt automation on Debian

#22
For anyone that wants to do this w/ nginx, you can add this location configuration to any "server" block for the challenge portion:

        location /.well-known/acme-challenge/ {
		alias		/var/www/acme-webroot/.well-known/acme-challenge/;
	}
Then use this this tool from mozilla to get a configuration for installing the cert: https://mozilla.github.io/server-side-tls/ssl-config-generat...

Re: Let’s encrypt automation on Debian

#23

Isn't Let's Encrypt supposed to launch the open beta today? Let's hope it actually happens...

You can sign up for the private beta and get access pretty quickly: https://docs.google.com/a/allaboutapps.at/forms/d/15Ucm4A20y...

I doubt they're even going to approve any more in the next hour and a half before they flip it to the public beta.

Re: Let’s encrypt automation on Debian

#24

Isn't Let's Encrypt supposed to launch the open beta today? Let's hope it actually happens...

You can sign up for the private beta and get access pretty quickly: https://docs.google.com/a/allaboutapps.at/forms/d/15Ucm4A20y...

I signed up for a few domains early on and they were enabled, I signed up for two more two days ago but haven't heard back yet.

Re: Let’s encrypt automation on Debian

#25
post #19
post #6

FYI, if you don't want to install all the dependencies of the official letsencrypt client, I made a https://github.com/diafygi/acme-tiny

Head of Let's Encrypt here. I don't love the number of dependencies for our client either, we're going to work to reduce them.

Maybe you can consider getting someone at Let's Encrypt review diafygi's acme-tiny code and, if approved, propose it as an alternative on the Let's Encrypt site. This will be very useful for users who get turned off by the root requirement or the number of dependencies.

Re: Let’s encrypt automation on Debian

#26

Earlier quoted context omitted.

You can sign up for the private beta and get access pretty quickly: https://docs.google.com/a/allaboutapps.at/forms/d/15Ucm4A20y...

I signed up for a few domains early on and they were enabled, I signed up for two more two days ago but haven't heard back yet.

Perhaps because the private beta was closed two days ago: https://community.letsencrypt.org/t/beta-program-announcemen...

Re: Let’s encrypt automation on Debian

#27
post #17
post #2

I really hope letsencrypt doesn't delay the real solution - DANE.

It's not a good solution. https://www.imperialviolet.org/2015/01/17/notdane.html

The TL;DR of that is:

1. DNSSEC uses a lot of 1024-bit RSA signatures (those are relatively weak) 2. You can't monitor the certificates that CA's issue because anyone issue their own certificates.

The first issue seems valid, but fixable. The second is a weird thing to complain about because it is the entire point of DANE!

Re: Let’s encrypt automation on Debian

#28
post #19
post #6

FYI, if you don't want to install all the dependencies of the official letsencrypt client, I made a https://github.com/diafygi/acme-tiny

Head of Let's Encrypt here. I don't love the number of dependencies for our client either, we're going to work to reduce them.

No worries! Every time I see a Let's Encrypt thread on HN, there's always complaining about having to trust the official client with root access, webserver configs, dependencies, or whatever. So I made my clients (letsencrypt-nosudo, gethttpsforfree.com, acme-tiny) to shut those people up. My clients are not intended to serve the wider Let's Encrypt target audience, who probably don't know what a CSR is. But for those who do, I made clients that don't ask for the access/trust that the official client needs to serve its target audience.

Thanks for making Let's Encrypt and ACME!

Re: Let’s encrypt automation on Debian

#29

Isn't Let's Encrypt supposed to launch the open beta today? Let's hope it actually happens...

You can sign up for the private beta and get access pretty quickly: https://docs.google.com/a/allaboutapps.at/forms/d/15Ucm4A20y...

Let's Encrypt's closed beta is no longer accepting new applicants [0], but they are launching the public beta in just under 2 hours (6PM GMT/10AM PST)[1] at the time of this writing.

[0]: https://community.letsencrypt.org/t/beta-program-announcemen...

[1]: https://letsencrypt.status.io/pages/maintenance/55957a99e800...

Post reply on HN