6 ms·
Looking through the code and the issue tracker (https://github.com/letsencrypt/letsencrypt https://github.com/letsencrypt/letsencrypt) I can't help but think th
by zaroth 11y ago
Looking through the code and the issue tracker (https://github.com/letsencrypt/letsencrypt https://github.com/letsencrypt/letsencrypt) I can't help but think they are approaching this wrong... In an attempt to make the certificate install completely hands off and fully automated, they are baking in a tremendous amount of complexity on top of a fundamentally brain-dead simple process.
I need to generate a private key, send you the public key, and get you to sign it. Somewhere in there, I need to prove I have control of the HTTP server on the existing A record, or that I can add a DNS TXT.
I can't say I'm a fan of shipping a SimpleHttp server baked into the tool, listening on port 80 (so run as root) which is also trying to deal with account authentication at the same time as generating the CSR, scanning directories of private keys to try to figure out how to sign the ACME nonce, etc. Getting this 'letsencrypt-auto' process to be able to receive and respond to HTTP requests on my domain is a different class of problem than getting a specially crafted file into a specific path on my domain. The former is clearly much more difficult in production than the latter....
Why not simply a script which;
- Takes as it's input the CSR and privkey files
- Does an HTTP GET to retrieve the ACME nonce
- Sign the nonce, generate the file you need to put on your webserver and tells you
the path to put it.
- Prompt to 'Press ENTER once the file is in place...'
- HTTP GET to indicate file is in place, server verifies, and returns the completed
full-chain cert.
(An optional parameter with a path to copy the signed-nonce file would make the script non-interactive.)
This could be written in a few lines of bash, right, assuming you could find an openssl command line which could sign the nonce in the correct form?
Keep in mind you have to repeat this process every 6 months with your live site, so what we want are simple composable / pluggable tools which don't try to own too much of the overall process, right?
Alternatively, ship two separate scripts (le-verify, le-certify) which create the ACME validation file and retrieve the cert once the file is in place, respectively.
I'm also not quite sure, why is there any concept of a user account on letsencrypt at all? Hopefully it is optional, I don't see what in this process requires that I register an "account" with them?
- akerro 11y ago>Keep in mind you have to repeat this process every 6 months with your live site, so what we want are simple composable It's just a script that must be run as specific user from specific directory, don't see a reason why it can't run from cron. > why is there any concept of a user account on letsencrypt at all? Hopefully it is optional, I don't see what in this process requires that I register an "account" with them? I got accepted to beta tests last week, I got allowance for 4 domains, 3 of which are public, one is commercial, one for my blog and one for ownCloud. They run on HTTPS TLS1.1 and TLS1.2 only. I didn't even know there are accounts.
- deleted 11y ago[deleted]
- Strilanc 11y agoThe whole point of let's encrypt is to be fully automated. Without that, it's just yet another crypto tool with poor usability.
- zaroth 11y agoI thought at least part of the point was eliminating the cost factor with strong crypto controls on the backend on a widely accepted CA with a sane process for validating ownership (ACME). There is a case to be made for ease of use, but I don't think they are broadening the horizons for TLS by making it as easy as "sudo letsencrypt -d www.example.org auth". Because 9 times out of 10 when you enter that command the first thing that will happen is 'port already in use'. Now what, shut down the production server? Or, trust this [1] to parse and edit my config files directly? Now, tell me they created a Wordpress plugin which you install, activate, and magically you now are running TLS, and I am 100% with you. That's a package which makes 100% sense to me. But there's no 'git pull' or 'sudo' anywhere in there that an end-user would see or have any clue about. If the person installing or renewing the cert is trying to decide, what should I type here... user@www:~$ Then I think the answer is not what they are currently shipping. Give me a tool which lets me generate the ACME validation file, and then a second command to pull the cert once the file is in place. Two bash scripts which don't even need 'sudo' to run. Save the "full automation" for things like Wordpress plugins, not the shell. [1] - https://github.com/letsencrypt/letsencrypt/blob/master/letsencrypt-nginx/letsencrypt_nginx/configurator.py https://github.com/letsencrypt/letsencrypt/blob/master/letse...
- ryan-c 11y agoRequiring the script to be run as root is a design decision, and I highly doubt it will be changed. They use the fact that the script is able to bind a privileged port (80) to prove it's being run as root so that chaos does not ensue in shared hosting environments.
- Avernar 11y agoYet their diagram shows that putting a signed file in the webroot of your domain is what's needed to prove you own the domain.
- veeti 11y agoThe client has a "manual" mode as you describe, but it's practically undocumented right now. It lets you create the certificate on any machine and leaves serving the verification file up to you. I do hope they polish it up or at least properly document it for the launch.
- dingaling 11y ago> Keep in mind you have to repeat this process every 6 months Actually every 90 days and they're talking about reducing that cert lifetime further still so as to encourage use of the automated tool. No way am I going to run a root tool in production and the alternative of manually running it for every server every 60 days or whatever is infeasible. A good concept made unattractive through pushing a mandate.
- diafygi 11y agoBoom, done. 428 lines. Only python and openssl as dependencies. https://github.com/diafygi/letsencrypt-nosudo https://github.com/diafygi/letsencrypt-nosudo It takes a CSR and user public key as input. Then, it prints the signing commands you need to run (so it doesn't have to know your private keys). Then, prints the command you need to run on your server. Finally, it prints your signed cert. Enjoy! The official Let's Encrypt client is aimed at an audience that doesn't know what a CSR is. For those that do and just want their free certs, I wrote this script to them to get their free certs without having to trust any client.
- zaroth 11y agoSweet! The part where you generate the code to run the HTTP server... can that also be done by generating a file which you copy to the existing server's root directory? Wow, ACME protocol seems way over-designed for what was actually required.
- feld 11y agoThanks for this, I just integrated it with my CSR script and now I have a SAN cert Just need to figure out renewal now
- foxhop 11y agoThank you for writing this alternative program and quickly responding to help in the issue tracker. This program's workflow feels much more pleasant for an admin who knows how TLS works. Is it possible to serve a text file on the existing server rather then taking it down for the python web server?
- AndyMcConachie 11y agoMy guess is that in the future distro/OS maintainers will just incorporate this into the as normal packages. I signed up for the beta, but was bummed that it's not yet supported on OpenBSD. I thought I would implement it, but because of dependencies that don't support OpenBSD(psutil) I couldn't. I commend their efforts, and I'm sure this will get more people to deploy TLS. But I don't think we're the intended audience of their auto client. I just want a key that's signed, and like you I'm not willing to let soem script touch my configs. My Apache configs are highly customized, so they'd probably break anyways. I'm going to check out what diafygi has written.
- M4v3R 11y agoIs there any specific reason they are using port 80, instead of some high, unused port, which would not require root privileges to open?
- shawabawa3 11y agoI believe so that a user on a shared host can't get a certificate issued for other user's sites edit: I'm not sure why it doesn't prompt you for a replacement port if 80's in use, as long as that port also requires root permissions to use
- Avernar 11y ago> Keep in mind you have to repeat this process every 6 months Renewal and revalidation are not the same process. Unfortunately they're thinking about making the revalidation period 90 days as well. That would suck as I have several sites where the content is generated by a script which would have to be disabled to serve a file.