8 ms·
Let's Encrypt Overview
- schoen 11y agoThis is a lovely and very clear summary! Two notes, which I also sent to the author: * Renewal does work already, it's just not documented anywhere. There is a script that can check when your cert is a specified amount of time from expiry, get a new cert, and subsequently deploy the new cert by updating symlinks. This mechanism works now, if the script is run from cron. * You can use the client on a machine that doesn't have Nginx or Apache, it just won't be able to install the resulting cert. But the client's standalone mode can obtain the cert and save the associated files in the current directory. (In this case, they also won't be enrolled for automated renewal by the renewer script.)
- hencq 11y agoHow would it work on for instance App Engine, where you can't really run a script on the server? I guess you'd have to manually do the validation step, but will it do any of the other steps automatically still?
- schoen 11y agoDepending on the nature of the control that you have over the site, you might need to get the hosting provider to do it for you (some of them are probably going to integrate Let's Encrypt) or you might be able to make the changes manually to prove control of the domain. If people think of useful integration features for particular platforms, we can take patches, or those platform developers can write their own clients. :-)
- selamis 11y agoI would love to tinker with this, but I wouldn't take the risk since it is not finished: "I guess because it isn't done yet" indeed.
- lebrad 11y agoThis is a really useful breakdown of Let's Encrypt and its scripted process for procuring certificates. It's ironic though that cryptologie.net is not run over https! They should use Let's Encrypt.
- jokr004 11y agoI love that the author of this article actually got out a pen and paper, drew out that diagram and photographed it. Great summary, looking forward to using this service!
- what_the_diffie 11y agoGive it a few minutes, someone will make an OCR to ASCII art app.
- ikeboy 11y ago>One of the common one is to upload a certain file at a certain address of that domain. I wonder if this can be socially engineered/tricked to gain a certificate for someone else's domain. Like, I've seen at least one service (Majestic Seo) that asks you to upload a document to your domain to get certain services. Now that this (will soon) exist, any such service that someone uses can generate a cert and MITM the site. Also, if they're verifying over http, couldn't anyone just mitm the verify connection? Well, anyone with access to any computer along the route between Let's Encrypt and whatever domain they want.
- iancarroll 11y agoThis (file upload) has been part of the CA/B Baseline for some time and most CAs already let you do it.
- gandarojin 11y agoI guess that’s why they will probably not use HTTP for the verification. Why would they? The client already generated a certificate and sent it to Let’s Encrypt, they can already use TLS.
- ikeboy 11y agoBut you don't know that this is the client. If all you're trusting is the cert they already generated, how do you know it's not an attacker?
- gandarojin 11y agoYou’re right, I did not think this through…
- eslaught 11y agoExcept the cert used in that process is one uploaded by the user, and could easily be provided by an attacker. As long as the attacker can MITM the path to the domain's web server, they can provide that cert for TLS and successfully spoof the site. Edit: Ok, technically it's a CSR signed by a private key, but you could still use the key to self-sign a cert or something... But none of that mitigates the MITM attack described above.
- BinaryIdiot 11y agoInteresting but will there be a way to generate the certs and download them myself versus running an application as root on my servers? I would much prefer not to run their application as root on my servers :)
- baby 11y agoSince the protocol is pretty open, you can code your own tool to communicate with the let's encrypt CA.
- StavrosK 11y agoAlternatively, it could have a non-sudo mode that would give you the certs and configs in a directory and tell you where to copy them (or generate a simple, five-line bash script to copy them).
- dcosson 11y agoAgree. I love what they're doing but it seems crazy that installing a new daemon and running it as root is being advertised as a key part of the solution. I get that they're trying to make it super simple for the hobbyist at home with a LAMP VPS but it feels like this should be an alternative to a simple, composable command line tool that's more of the unix philosophy and less invasive. The good thing is the ACME protocol looks pretty straightforward so I'm sure someone will write that tool, even if Lets Encrypt themselves aren't interested in providing it.
- davidgerard 11y agoWe are desperately looking forward to this being available so we can SSL all our dev sites and still be able to test them on our phones (which are a bit hard to get one's own CA cert onto).
- michaelt 11y agoIt sounds like Lets Encrypt is going to require a site to be publicly available for them to give out a cert for it. They'll tell you to put a certain file at a certain location to demonstrate that you control the domain. So unfortunately it'll only help with your dev sites if they're available on the public internet.
- teddyh 11y agoNo, that is only one of the four methods of proving domain ownership; see the ACME protocol specification: https://letsencrypt.github.io/acme-spec/#rfc.section.6 https://letsencrypt.github.io/acme-spec/#rfc.section.6
- schoen 11y agoHowever, the methods described there that don't involve a domain validation step all specify prior ACME usage; that is to say that at least the first time you get a cert from an ACME CA with policies akin to those described here, you must always complete a DV step with DVSNI or Simple HTTP (which do require a publicly-visible server with a publicly-visible domain name).
- teddyh 11y agoWhat about the method in section 6.4: DNS? That certainly does not require either a prior ACME usage or a publicly-visible server.
- schoen 11y agoThat's a good point. I don't expect the Let's Encrypt CA will be willing to help keep servers (or certs issued to them) a secret -- for example, the certs are likely to be published in Certificate Transparency! -- but you're right that the ACME DNS challenge doesn't require the server to be publicly accessible and doesn't even require the underlying subject name to exist in the publicly-visible DNS.
- diafygi 11y agoFYI, if you don't want to install the official Let's Encrypt client on your production server, I created a simple python script that will automate the ACME process for you. It doesn't have to run on your server, and it doesn't ask for your private keys. https://github.com/diafygi/letsencrypt-nosudo https://github.com/diafygi/letsencrypt-nosudo The only thing that has to be run as sudo on your production server is a simple python one-liner that temporarily serves the required file. The script prints out this one-liner so you can copy and paste it into your server's terminal, then kill it when the challenge is done.
- garrettr_ 11y agoHow is this different from/superior to Let's Encrypt's built-in "standalone authenticator"? [0] [0] https://github.com/letsencrypt/lets-encrypt-preview/blob/master/letsencrypt/plugins/standalone/authenticator.py https://github.com/letsencrypt/lets-encrypt-preview/blob/mas...
- diafygi 11y agoThe standalone authenticator still requires (1) installing/running the letsencrypt client on your production server, (2) letting it run as root, and (3) letting it access your private keys. My script requires none of these things.
- kyledrake 11y agoI would add that it's also easier to understand. I've been having a lot of trouble figuring out ACME's workflow. This has been pretty helpful.
- JoshTriplett 11y agoDoes your script support doing the DVSNI challenge instead, to avoid needing to install a file on the web server?
- diafygi 11y agoIt used to, but that meant you had to scp the generated dvsni cert to your server[1], which is more complex than asking the user to start serving a string over a specific url (which is what the SimpleHTTP challenge requires). [1]: https://github.com/diafygi/letsencrypt-nosudo/blob/9607deb7b259499725ce1c705a1664199f51881d/sign_csr.py#L149 https://github.com/diafygi/letsencrypt-nosudo/blob/9607deb7b...
- StavrosK 11y agoDoes anyone know when exactly it will be released? It says Mid-2015, and it's almost past that.
- ohitsdom 11y agoI'm really excited about this project, but a lack of steady updates and communication on release date are really hurting it. Hopefully they release soon and make this a moot point.
- StavrosK 11y agoI kind of agree, but I also don't like hearing things about services I really want but can't try out yet, so I'm on the fence. They do run things in the open, though, and development is open source, so I think the updates have been pretty good...
- baby 11y agoThey just released a blog post about generating the certs. That means they are getting their. From looking at the code they have most of it in place, they just lack a few features, and testing. IMO it shouldn't take too long now. The first commits date from october of last year.
- Hello71 11y agoif you divide the year into 3 equal parts, early, mid, and late, then early is January through April, mid is May through August, and late is September through December. therefore, they still have two and a half months approximately until "mid 2015" is over.
- ohitsdom 11y agoGood question from the page's comments- will this work for different sites run on one server? I'm thinking of all my side projects that have sites up, they're all run off the same $9/month Apache server. Can I get individual certs for each domain run off the server?
- bifurcation 11y agoYep, that should work fine. You'll just need to do the validation process for each domain.
- ohitsdom 11y agoI saw in an earlier thread that wildcard certs won't be supported at first, but possibly in the future. An additional comment was made that wildcard certs wouldn't be necessary once the cert issuing/renewal process is automated. My question is: wouldn't wildcard certs be faster if the behavior on your site skipped around different subdomains? One certificate for all vs individual certs for each subdomain. I may be way off, I'm a novice when it comes to SSL/TLS handshake so please correct my ignorance.
- derefr 11y agoMaybe the question is wildcard vs SAN certs. With automated cert issuing/renewal, they could theoretically talk to e.g. Cloudflare's API to get your DNS records, if you're with them, and then regenerate a new SAN cert containing exactly the subdomains you really have whenever that list of subdomains changes. Which is probably more secure in some way I don't understand. You're right about the "just using a bunch of separate certs" solution being slower, though, especially with HTTP/2 (which, because of origin combining, uses exactly one real socket per TLS cert.)
- tombrossman 11y agoLet's say you host your site on your own server at www.example.com. You want that to be served by HTTPS. You also have a subdomain cdn.example.com for static assets which is CNAME'd to a proper CDN that you want to use HTTPS with also. With a wildcard cert, the third-party CDN would need your private key for your self-hosted www.example.com site. With different keys & certs per-site, the process is more modular. I agree that wildcard certs would be great and I'll default to using them for the simplicity (e.g. temporarily activate a quick test.example.com site to check something works) but the ability to keep things modular is also great.
- derefr 11y agoQuestion: is the X.509 system set up in such a way that one of these issuers could give me a free code-signing cert, or a free CA cert for signing client certificates? Because, as far as I understand, the answer is no: signing certs have no sense of signing "for an origin". If a CA issued me a CA cert, I could use it to create a signed cert for microsoft.com. Which seems nonsensical. All I want is to get issued a CA cert that lets me sign arbitrary things within my domain's scope. Basically, the X.509 equivalent of a DNS NS record, delegating responsibility for making assertions about that domain (and only that domain) to "my" CA. Why is that so hard?
- icebraining 11y agoI believe that's the point of the Name Constraints property, but from what I can tell it's generally ignored.
- JoshTriplett 11y agoIn particular, there are enough stacks that ignore it that it would be unsafe to issue a CA certificate even with nameConstraints.
- grahamedgecombe 11y agoX509 extensions can be marked as critical. Certificates must be rejected if the stack encounters a critical extension it doesn't understand. (In theory at least, I haven't looked at real implementation behaviour.)
- dtech 11y agoSo then you've jumped from the frying pan into the fire, since your cert now will not work in those implementations.
- baby 11y agoThey only sign leaf certs
- lurkinggrue 11y agoDoes anybody know how this handles multiple domains and multiple domains on one IP?
- schoen 11y agoYou can get certs that are valid for multiple domains, using subjectAltName (SAN). The client can request multiple names at once and the resulting cert will be valid for each.
- ex3ndr 11y agoAs I understand they use HSM for signing certificates. What will be if they destroy HSM? How they can continue to operate?
- kstenerud 11y agoI'm a bit confused on the issue of certs because I've heard that they don't work for subdomains, so can anyone tell me: If I get a cert from someone like letsencrypt for a domain I control, for example "xyz.com", will that same cert also work for "wiki.xyz.com", "blog.xyz.com", "someotherthing.deepdomain.xyz.com" and so on? I'm interested because I use jwilder/nginx-proxy and then have a docker container for each of my webapps, each connected to a different subdomain (video, music, rss, vm, desktop, files, etc).
- schoen 11y agoNope.
- wolf550e 11y agoFor a browser to accept a cert while connecting to "wiki.xyz.com", the cert needs to be for "wiki.xyz.com" or for ".xyz.com". Note that ".*.xyz.com" is invalid. So called "wildcard certs" are usually more expensive than single and multi-domain certs.
- nickodell 11y agoYeah. And there are cases where a single wildcard isn't enough, like stackexchange's meta sites. If you type in https://meta.<site https://meta.<site name>.stackexchange.com, it will return an SSL error.
- garrettr_ 11y agoThere are several ways to resolve this issue: 1. Get a separate certificate for each subdomain. Let's Encrypt makes this feasible since the certs are free and require a minimum of human overhead to obtain. 2. Get a single certificate that covers each subdomain by using Subject Alternative Names, which are currently supported by Let's Encrypt. 3. Get a wildcard certificate for "*.xyz.com". Let's Encrypt does not support this and I do not think it plans to, at least not in the initial release. The main question is - is the set of subdomains known before-hand, or is it highly dynamic? If it is fairly stable, then options 1 or 2 will work well for you; otherwise, you probably want option 3. Choosing between option 1 and 2 usually depends on the details of your infrastructure and your threat model. For example, are all these subdomains served from the same server or different servers? If it's the same server, you might be more inclined to use 1 cert for all of them (option 2) since it will be easier to manage. Do all the domains have the same threat model? For example, what if you run blog.xyz.com on one server and billing.xyz.com on a separate, hardened server. In that case, you would want option 1 because if you used the same cert on both servers, obtaining the private key from the less-secured blog.xyz.com server could be used to attack traffic for billing.xyz.com.
- makmanalp 11y agoSo now that you can even get EV certs for free, what does this mean for the SSL Cert industry? Are they quaking at the knees or do they not care?
- hueving 11y agoCan someone explain why the CSR is exchanged over https? The whole point of a CSR is that an adversary can't fake it and get a key that works for you and the adversary.
- dadrian 11y agoThe CSR is signed by the key that is going to be used for HTTPS on the website requesting a certificate. If the CSR wasn't transmitted over HTTPS, since the Let's Encrypt CA has no idea what your key is, a network adversary could replace your CSR with one containing an attacker-controlled key.
- stephenr 11y agoIt would be nice if they offered certificates for S/MIME signing + encryption too. Edit: sed "s#g/e#g + e#g"
- TazeTSchnitzel 11y agoIt took me a moment to realise that wasn't a sed command replacing "MIME signing"(???) with "encryption".
- stephenr 11y agoHa! I didn't even notice that as I was typing!
- kyledrake 11y agoHas anyone tried a ruby client library implementation yet? I've looked at the spec and it's pretty complicated. I'm not sure I'll have the time to devote to it unfortunately.
- StavrosK 11y agoWhy rewrite it? What's wrong with the current implementation?
- kyledrake 11y agoThe current implementation is fine for people running nginx servers with a single domain, but for anyone trying to engineer this via a web application for more than one domain, this is not sufficient for proper tooling.
- StavrosK 11y agoOh, you mean an actual gem? I see. I hope the current implementation is importable from Python, as well.
- kyledrake 11y agoThis python script is informative: https://github.com/diafygi/letsencrypt-nosudo/blob/master/sign_csr.py https://github.com/diafygi/letsencrypt-nosudo/blob/master/si... A good start for trying to figure out the workflow.