8 ms·
Announcing Certbot: EFF's Client for Let's Encrypt
- schoen 11y agoThis is the new name of what was previously known as the official Let's Encrypt client.
- WhatsName 11y agoWhich was a lot more straight forward, so why change it to something obscure? (I mean "Let's Ecrypt" is a well positioned brand and since this is all about trust, why introduce a new name?)
- detaro 11y agoBecause it's supposed to be independent of the Let's Encrypt brand, with Let's Encrypt hopefully being one of multiple providers of CAs speaking the ACME protocol and this client being one of many clients compatible with them. There has been a lot of misunderstanding and FUD about how you can use Let's Encrypt because of the relatively heavy and by default "invasive" official client. This hopefully helps to make it clearer that it is one option of many.
- pde3 11y agoThe official client (now Certbot) actually supports a whole bunch of different use cases; some people want full automation of everything; other people find that "invasive". The software supports both, but people would often find the wrong instructions. The new Certbot landing page tries to do a much better job of giving people instructions that are tailored to their use case and needs. Please try it and send us feedback! https://certbot.eff.org https://certbot.eff.org
- ceejayoz 11y agoGiven the emphasis on full automation in Let's Encrypt, it's really baffling that the official client lacks DNS-based support at this time. Anyone behind a load balancer like AWS ELB can't really use it.
- Namidairo 11y agoThis along with IPv6 are probably one of the two most visible issues right now.
- scrollaway 11y agoIPv6 support has recently been completed in Boulder (the LE CA software) already: https://github.com/letsencrypt/boulder/issues/593 https://github.com/letsencrypt/boulder/issues/593 That was the main blocking issue. IPv6 in LE is coming very soon.
- nbevans 11y agoSame. The current approach of placing a file on a HTTP endpoint is basically a joke, right?
- niij 11y agoCan you please explain why that is a joke? (I am assuming you are saying the LE verification isn't secure)
- pfg 11y agoHTTP-01 verification works quite well behind load balancers - it's a simple GET request to a specific URL. You're probably thinking of TLS-SNI-01, which requires changes on the host that's terminating TLS (which isn't possible on a load balancer unless it has dedicated support for ACME).
- ceejayoz 11y ago> HTTP-01 verification works quite well behind load balancers - it's a simple GET request to a specific URL. Running the client on one of the servers frequently results in it hitting one of the other servers in the cluster. It's a pain in the ass - you either rely on luck and retry a number of times until it hits the right server, or you have to go the more manual route and deploy the challenge directory to all of the servers. DNS doesn't care how many servers there are, as long as there's the right record in place.
- mcguire 11y ago"Since it doesn't seem like your operating system has a packaged version of Certbot, you should use our certbot-auto script to get a copy: wget https://dl.eff.org/certbot-auto chmod a+x certbot-auto "certbot-auto accepts the same flags as certbot; it installs all of its own dependencies and updates the client code automatically." I don't know whether to be terrified or horrified.
- pde3 11y agocertbot-auto (previously known as letsencrypt-auto) is definitely a hack -- it allows people to run the client on typically older OSes that don't have backported native packages. It's basically a tiny autoupdate and packaging system written in bash and python. It uses airgapped signatures for updates, checks sha256 hashes for all of the python dependencies it's installing, and puts them into a python virtual environment so that they don't affect your OS. If you don't like wget; chmod, you can check a gpg signature too: https://certbot.eff.org/docs/intro.html#installation https://certbot.eff.org/docs/intro.html#installation
- pde3 11y agoOh, and it's in use on 500K - 1 million webservers. So extra eyes auditing it are always welcome :)
- majewsky 11y agoWow, that's really cool. I remember digging through the documentation for days to get everything set up on my systems (nginx on Arch Linux). Now this thing gives me the same information in just two clicks, which is a massive improvement.
- pfg 11y agoThis blog post[1] explains the motivation behind the name change (and moving the project to the EFF). [1]: https://letsencrypt.org/2016/03/09/le-client-new-home.html https://letsencrypt.org/2016/03/09/le-client-new-home.html
- notatoad 11y agoAn official client implies that other implementations of the standard are unofficial. Building a monoculture around a single client isn't healthy for the project, and nobody wants to put an unofficial client into their security infrastructure.
- nickfrostatx 11y agoOne problem I have with this tool is support for pre-computed public keys or CSRs. The client prefers to generate a new key pair for every certificate. Automated renewal that works the same way for existing CSRs as it does for regular certificates requires undocumented hacks. Using the same key pair for multiple certificates is necessary for public key pinning, since Let's Encrypt only issues certificates that last 90 days. I would love to see this feature get developed further.
- schoen 11y agoThere is code in the client to reuse a keypair when renewing (without needing to reuse a CSR); there's just no way to trigger that from the UI so far. Maybe I'd better add one soon.
- pde3 11y agohttps://github.com/certbot/certbot/issues/2373 https://github.com/certbot/certbot/issues/2373 (if you want to reuse a CSR; reusing the key is probably easier)
- pred_ 11y agoIt's worth pointing out here that reusing a static keypair with Let's Encrypt is currently more or less straight-forward using acme-tiny. https://github.com/diafygi/acme-tiny https://github.com/diafygi/acme-tiny Edit: Looks like https://github.com/lukas2511/letsencrypt.sh https://github.com/lukas2511/letsencrypt.sh is capable of doing the same, as pointed out in another comment.
- theandrewbailey 11y ago> Using the same key pair for multiple certificates is necessary for public key pinning, since Let's Encrypt only issues certificates that last 90 days. So do like Github does (did?)[0], and make the pins valid for 5 minutes. [0] looks like they upped it to 60 days?
- oarsinsync 11y ago> So do like Github does (did?)[0], and make the pins valid for 5 minutes. That kinda defeats the point of HSTS. If the key is changing regularly, it makes it easy for an attacker to just temporarily prevent access to the site for long enough for the pin to timeout, and then present their own certificates and keys.
- deleted 11y ago[deleted]
- hackuser 11y ago> Let’s Encrypt is a certificate authority, co-founded by EFF, Mozilla, and researchers from the University of Michigan I'd like to make a point about money: Institutions like these need money, or many important public goods will never exist. Consider that next time you are making donations or your legislators want to cut funding.
- maerF0x0 11y agotinhat on. Also consider where they get most of their money.
- Freak_NL 11y agoPlease elaborate if you suspect ulterior motives.
- dev1n 11y agoEFF receives donations from DPR2 [1]. [1]: http://motherboard.vice.com/read/the-secret-life-of-a-silk-road-20-mastermind http://motherboard.vice.com/read/the-secret-life-of-a-silk-r...
- Freak_NL 11y ago> This is because he says he donated hundreds of thousands of dollars to a wealth of different organisations and charities. Those included the Tor Project, the nonprofit that maintains the Tor software, and some entities with no immediate link to technology or drug policy, such as a children's home. (The Tor Project did not respond to multiple requests for comment.) No direct mention of the EFF, but I'll take your word for it. Of course even if Assad, Erdoğan, and Putin donate money to the WWF, that does not mean saving panda's is a bad thing.
- lobo_tuerto 11y agoSo what? now the project is _tainted_?
- 11y ago
- mxuribe 11y agoI had been interested in Let's Encrypt, but hadn't dove in. This makes implementation alot more compelling.
- jbergstroem 11y agoFor people that want something much smaller (dependency-wise), I can recommend letsencrypt.sh which – together with cron – achieves the same goal: https://github.com/lukas2511/letsencrypt.sh https://github.com/lukas2511/letsencrypt.sh
- emilong 11y agoletsencrypt.sh is great. It has easy support for existing CSRs and can do dns-01 verification (i.e. making sure you control the domain via a DNS secret rather an http get path/secret). I wrote up a usage tutorial for the latter with Route53 here https://blog.boldlisting.com/free-ssl-certificates-without-placing-a-file-on-your-server-using-aws-route53-31035f8fca14 https://blog.boldlisting.com/free-ssl-certificates-without-p...
- jalami 11y agoI use acme-tiny[0] and it was pretty simple to setup. The letsencryptclient requires running as root and quite a few dependencies if I remember correctly. I have acme-tiny run with its own private user privilages monthly in a cron job and it's pretty slick. Only has access to the account key and writing to the http challenges and cert directories, no private key access. [0] https://github.com/diafygi/acme-tiny https://github.com/diafygi/acme-tiny Edit: clarification
- majewsky 11y agoThe letsencryptclient does not need to run as root. I run it below its own user and group, and add that group to the http user to allow it to read the certificates and keys. Configuration at https://github.com/majewsky/system-configuration/blob/master/hologram-letsencrypt.pkg.toml https://github.com/majewsky/system-configuration/blob/master... and https://github.com/majewsky/system-configuration/blob/master/hologram-nginx.pkg.toml https://github.com/majewsky/system-configuration/blob/master... Permissions are more granular on your setup, though, as far as I can see.
- jalami 11y agoLike I said, I haven't used the their client, just going off what I've come across in researching it briefly. Something must have changed then, there are multiple ways to configure it, or what I read previously was just wrong. I thought that was why repos like https://github.com/diafygi/letsencrypt-nosudo https://github.com/diafygi/letsencrypt-nosudo existed for a time. That's good news nonetheless.
- pde3 11y agoYes, there are definitely multiple ways to configure it. We focused first on working successfully for as many people as possible, which meant shipping the letsencrypt-auto wrapper script which requires sudo. But with some extra work you can definitely run Certbot as a non-root user, and we're working with the OSes that package us to have Certbot operate with something like ssl-cert group privileges in many situations in the future.
- Perceptes 11y agoThis new name and website are a big improvement to the branding of the client, and make it clear that this client is not a requirement for getting a certificate from Let's Encrypt. It was very difficult to explain to people learning about it that there is a difference between: 1. Let's Encrypt, the certificate authority 2. ACME, the protocol for users to interact with Let's Encrypt 3. Boulder, an implementation of an ACME server in Go that Let's Encrypt uses 4. Certbot (formerly the Let's Encrypt client), a command line client and ACME library for Python, originally developed by the Let's Encrypt team Any CA can use ACME to offer automated certificate issuance to their users. Anyone can implement an ACME server or client in any language. There is no "official" client or server necessary. It's also important that Certbot was rebranded to distance it from Let's Encrypt because, personally, I think the project is doomed to fail. It tries to handle both certificate issuance and configuration of software using certificates. It attempts to abstract the process for someone who barely understands what certificates/SSL/TLS are (if at all), but requires so much detail from them in order to configure and run the client that they might well have just learned how it worked in the first place. In other words, Certbot's use case targets laymen, but requires non-layman understanding to use. It doesn't help that their documentation is very badly organized and confusing, often mixing content for the CLI and the Python Library, which have different audiences: end users and developers building an automated tool in Python. Meanwhile, intermediate and advanced developers and system administrators who understand the concepts are much better served by a different client that simply takes care of certificate issuance without trying to automatically manage the software they will be using the certificate with. There are many, but so far I've been happy with Lego (https://github.com/xenolf/lego https://github.com/xenolf/lego).
- pde3 11y agoI think your criticisms were pretty fair of the earliest releases of the Let's Encrypt client, but they seem to be less accurate now. We see the client (aka Certbot) being used successfully by many hundreds of thousands of site operators. In terms of full automation, the Apache plugin has gone from "experimental" to "works for most people automatically". We'll be working on delivering similar features for Nginx next. But if lego works for you; that's great!
- pricechild 11y agoI've found acmetool perfect for my use and this table explains why: https://github.com/hlandau/acme#comparison-list-of-client-implementations https://github.com/hlandau/acme#comparison-list-of-client-im... The biggest feature the official letsencrypt client was missing was triggering restarts of other services after certificate renewal.
- pde3 11y agoHooks to perform arbitrary restarts and housekeeping upon renewal were added in version 0.5.0. Run with "--help renew" and/or see https://certbot.eff.org/docs/using.html#renewal https://certbot.eff.org/docs/using.html#renewal
- anc84 11y agoIf the EFF and Mozilla had not veered into the militant feminism/PC thunderstorm, I would not have cancelled my recurring donations.
- vtlynch 11y agoYou are ignorant.
- dang 11y agoPlease don't respond to a bad comment by making the thread worse.
- dang 11y agoWe detached this subthread from https://news.ycombinator.com/item?id=11687746 https://news.ycombinator.com/item?id=11687746 and marked it off-topic.
- anc84 11y agoI understand that my reasons might trigger some people's reactionary instincts but how is a post about my reasons not to donate to the EFF anymore off-topic in a thread about donating to the EFF?