8 ms·
Let's Encrypt ACMEv2 and Wildcard Launch Delay
- berbec 9y agoCrap. I had certs set to expire on 2/28! I was going G to be saved by wildcard. Off to make a bunch of DNS entries....
- mustardo 9y agoThat's ok you still have almost 26 months ;-p
- tty7 9y agoslow clap :D
- schoen 9y agoDoes your ACME client already support ACMEv2 and wildcards? I think only acme.sh has so far claimed to (happy to be corrected if another client has finished its implementation).
- berbec 9y agoI use certbot. I'm not sure as I was just planning on figuring it out for the night of expiration.
- schoen 9y agoI'm part of the Certbot team and I can tell you that the ACMEv2 support is still being implemented by my colleagues now; even if it had been included in a release this week or next, you would have been cutting it pretty close! Many of our users don't have the most current release because distribution packagers don't ship it right away (or even for months or years, depending on circumstances). Certbot's own autorenewals (which I originally implemented and which I hope are currently working for you -- I'm happy to try to find a way to get them to work in your deployment if they're not!) try by default to renew certificates 30 days before expiry in order to give people a lot of time to notice and intervene if something goes wrong. Consistent with that, I'd encourage all of our users not to rely on anything happening less than 30 days before expiry as part of their plan for keeping certificates current on their sites.
- berbec 9y agoThank you for all your work. My renewal went through fine. I had commented it out of crontab, but went fine once I ran it. I was pleasantly surprised when tls-sni worked flawlessly.
- schoen 9y agoGreat! One thing to know about the TLS-SNI situation is that TLS-SNI-01 has been disabled for new issuance and only works for renewals. The selection of authentication methods is pretty transparent because the ACME protocol allows the CA to state which methods it will accept for a particular domain authorization (so for the renewals it can state that TLS-SNI-01 is permitted, while for new issuance it can state that it's not, and a client can respond accordingly). Apparently the ACME WG is working on a TLS-SNI-03 method that will be safer and that might be supported by Let's Encrypt (and ACME clients) at some point. But it's also possible that TLS-SNI-01 could be disabled in the future, even for renewals, even before TLS-SNI-03. So, if you happen to have anything in your setup that prevents the use of HTTP-01 on port 80 for authentication, you should be aware that renewals could potentially stop working at some point (although this isn't imminent), and that you might also have difficulty adding new domain names to your certificates. https://community.letsencrypt.org/t/important-what-you-need-to-know-about-tls-sni-validation-issues/50811 https://community.letsencrypt.org/t/important-what-you-need-... This unfortunate situation is a nice showcase of the ACME protocol's flexibility, because the CA has a way to tell the client very specifically what authentication methods to attempt or not to attempt for each domain (and if new methods are specified in the future, they can be rolled out incrementally without breaking compatibility).
- tialaramex 9y agoOne thing that'd be good here for outside observers is for Let's Encrypt to bake a list of the Blessed Methods used into certificates as OIDs in the Policy section. Right now a researcher with 5 million Let's Encrypt certificates can see which ones use public keys with unusual patterns, how many are for names in the French .fr TLD, how many have longer key lengths, and so on, but they can't see whether the validation was done with Method 10 (which had this unexpected flaw) or some other method. Another CA (can't remember which one) was looking at doing this, and it seems like it'd be nice for Let's Encrypt too.
- cm2187 9y agoIt’s not super hard to implement yourself, particularly given it is a variation of the first ACME protocol for which there is lots of code available, and the staging API for v2 is already up and running. The main challenge is that wildcards require DNS authorization, so a full automation is DNS api specific. My DNS (OVH) has a neat rest API. But given the variety of DNS providers and APIs it is going to be challenging to rely only on a reference implementation without wrtiting a little bit of code yourself.
- ocdtrekkie 9y agoIt's hard to complain about a slight deadline miss from an incredible project offering free stuff.
- tyingq 9y agoI am a little worried about the monoculture LE is creating. I don't have any bright and practical ideas to fix that, however. Short of some other consortium making an equivalent, but with different tech underneath.
- marcosdumay 9y agoFor TLS certificate authorities, a monoculture is way better than the alternative.
- tyingq 9y agoI'm thinking of some critical flaw in ACME, or CA outage, bad cert push, etc. I get your point, but I think there's a legit risk here.
- nodesocket 9y agoPrecisely the problem. Real companies mostly prefer to use paid solutions because they have comfort and confidence in knowing there is a business and backing behind it. At least I know I do. I never got the whole developer complex wanting and even expecting everything for free. Seems hypocritical and counter-entrepreneur. Also for what's worth, I've been deploying Let's Encrypt into production recently using Caddy and (on-demand) TLS and while it works, the rate limits being reset weekly is really scary and VERY VERY easy to hit. I know myself and my clients would be willing to pay for Let's Encrypt Pro (higher rate limits, etc). Take our money.
- ocdtrekkie 9y agoThat's not Let's Encrypt's role to play though. As a user, I'd be much more skeptical of an LE cert'd site than a Verisign cert'd site. That's not a knock on LE, that's just recognizing a higher barrier to entry. Let's Encrypt's goal is to get everyone encrypted, not necessarily to ensure everyone is who they say they are. And as a fellow person who does real business at times, I often prefer paid products because I know I can get support from the company backing it. I don't think Let's Encrypt will replace the entire CA industry, and I don't think it should. (As tyingq says, monocultures are bad.)
- sdrinf 9y agoWhile HTTPS is being burned into the architecture of the Web, I have a humble question to ask: what is the dear HN community's next-best-option in a scenario if letsencrypt dies/gets sued/goes under/servers not accessible anymore? I ponder on this question seeing how Google is planning to increasingly depreciate HTTP. While in general, I welcome the security upgrade, the lack of next-best-free-options makes me vary of this config change locking us into a $$$paid-only web publishing system.
- kemitche 9y agoACME is a protocol - I imagine most of us are hoping that, should LE fade off, one or more others take the reins and implement it.
- badrabbit 9y agoWith PKI,a good protocol isn't the problem but rather making the cost of infrastructure keep-up worthwhile. Anyways, non-pki protocols are in the works.
- sdrinf 9y ago> non-pki protocols are in the works. Could you kindly link to relevant threads / RFCs / orgs / undertakings currently working on that, please?
- aeden 9y agoDANE might provide a solution. See specifically the section https://tools.ietf.org/html/rfc6698#section-2.1.1 https://tools.ietf.org/html/rfc6698#section-2.1.1, certificate usage 3: 3 -- Certificate usage 3 is used to specify a certificate, or the public key of such a certificate, that MUST match the end entity certificate given by the server in TLS. This certificate usage is sometimes referred to as "domain-issued certificate" because it allows for a domain name administrator to issue certificates for a domain without involving a third-party CA.
- MertsA 9y agoAm I the only one who thinks the way we deal with certificates is just completely backwards? Why should there even be a CA at all for DV certs? We already have to trust the registrar as ultimately they can get whatever DV certs they want so why not just limit our trust to them instead of adding hundreds of additional organizations that can compromise our security? And we pay them for the privilege of doing this?? I get CAs for EV and OV certs, of course you need an additional trusted party there, but the vast majority of websites out there do not use EV or OV certs and to be fair users by and large don't even notice the difference between a DV and an EV certificate in the first place. We already have DNS, we already trust DNS to issue certificates to people, why don't we just cut out the middle man since they serve no additional purpose?
- BillinghamJ 9y agoThis is the idea behind DANE :) https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Na... Effectively, you’d serve a self-signed certificate, then use DNSSEC to state that the origin can use the self-signed cert. Then clients can use that without showing warnings. However, it does rely on DNSSEC not being a total failure, so not likely to end up in widespread use anytime soon unfortunately. Also, given the more recent growth of alternative solutions to the problems DANE solves, like Let’s Encrypt and CAA DNS records, I’m not sure we’re likely to see much more work being done on it sadly.
- technion 9y agoThe thing is that "control of the DNS" can mean different things. I have control of the DNS on my network, and at the local coffee shop. I can use that to attack users, but I cannot use that to obtain a certificate. I still agree with you in a sense, an alternate solution would be great. But we that middleman is the best we have right now.
- josteink 9y ago> The thing is that "control of the DNS" can mean different things. In every way this discussion is related, "control of the DNS" should mean control of the one authoritative DNS source, in a way which means that if a service across the internet requests a DNS record, it won't be affected by whatever DNS-trick your neighbourhood cafe's wifi may apply. Trying to muddle the discussion of a fairly straight-forward, reliable scenario with consumer-space DNS resolution is IMO not very productive.
- technion 9y agoIt's not mentioned, but I'm assuming this feature with the same original schedule: Embed SCT receipts in certificates Is also delayed? I think this has been quite underrated.
- discreditable 9y agoI've been following progress in their GitHub issue for it: https://github.com/letsencrypt/boulder/issues/2244 https://github.com/letsencrypt/boulder/issues/2244 Most recent comment: > We're working hard on it, but will probably not land this in production before the end of February. Still, we are very much aware of the upcoming deadline and committed to meeting it. Thanks for the enthusiasm everyone! :-)
- nickjj 9y agoI've been using LE from the start and it's been awesome (especially with clients like acme-tiny), but wildcards changes everything. How many of you are really going to set up a custom DNS updating script? Maybe I misread something but I remember hearing wildcard certs will only work with DNS based challenges. Wouldn't that mean the verification tool would need to support every single registrar's / DNS provider's API? For example, I host my domains (and DNS) with namesilo.com. Is a challenge script really going to know how to interface with their API to add / remove the TXT records? What about the 50 other popular DNS providers?
- gerdesj 9y agopfSense has a dynamic DNS updater built in with support for a huge number of services - https://doc.pfsense.org/index.php/Dynamic_DNS https://doc.pfsense.org/index.php/Dynamic_DNS . There's also an ACME client and HAProxy packages and a built in CA and cert handler. Its all open source, so grab their scripts ...
- yrro 9y agoIf only there was an existing standardized way to transfer zone updates to an existing DNS server...
- piracykills 9y agoYes, but there's already scripts handling many of the most popular. Check out acme.sh and remember, changing your DNS provider or hosting it yourself really isn't that bad. https://github.com/Neilpang/acme.sh https://github.com/Neilpang/acme.sh
- nickjj 9y agoNice, it looks like they support namesilo and ~40 others. So my suspicion seems accurate. The script will need to know how to interface with each provider and you (as an end user) will also need to be responsible for setting up your own API keys for whatever provider you use.
- 9y ago
- deleted 9y ago[deleted]