4 ms·
> the architects of LetsEncrypt do not depend on or, in reality, care about DNSSEC Key personnel from ISRG (the charity which builds Let's Encrypt) have HN acc
by tialaramex 7y ago
> the architects of LetsEncrypt do not depend on or, in reality, care about DNSSEC
Key personnel from ISRG (the charity which builds Let's Encrypt) have HN accounts, but mostly steer clear of contradicting HN Fan Favourite Thomas Ptacek because it's not worth it even when he says things which are directly contradicted by the facts.
However I am a sucker and will respond to point out, once again, that in fact Let's Encrypt obeys the ACME RFC in this respect (as well it might given that two of the RFC's editors are key personnel for Let's Encrypt and both ACME and Let's Encrypt are bound together from the outset) and so yes of course it does DNSSEC validation.
The anti-DANE lobby from browsers (which caused a pretty nasty scene for the TLS WG) doesn't change the facts which made DNSSEC necessary and that's why the solution for problems keeps being DNSSEC no matter how much you say it mustn't or shouldn't. The same browsers are currently working on ESNI which, punts the authenticity problem back to DNSSEC because that's the only way it gets done. And they're working on DNS records to drive HTTP/3 without Alt-Svc (and throw in ESNI at the same time) and those punt authenticity to DNSSEC as well, for the same reason.
No matter how hard you shove your fingers into your ears, the authenticity problem has to be solved in DNS and that's what DNSSEC does.
- tptacek 7y agoThis is needlessly uncivil. Please edit stuff like "HN Fan Favorite Thomas Ptacek" out of your comments in the future; I don't write that way at you, and the guidelines here tell you not to. I'm sorry that you aren't the only person in the world that knows people involved with CA operations, but, like you, I've been working in this field for "more than 10 years". If you read my short comment more carefully, you'll see that I didn't say that LetsEncrypt doesn't do DNSSEC. It does, unlike other CAs that claimed to do DNSSEC and then stopped. My point, of course, is that it doesn't matter, because nobody signs their zones. Since browsers are the only important customer of DANE, it's funny to see them referred to as "the anti-DANE lobby". Is it a "lobby" when it's the entire population? Were the Romans the "anti-Visigoth lobby"? Your premise that browsers using DNS means browsers will have to use DNSSEC is obviously flawed; browsers rely on DNS today, and not a single one of them does DNSSEC. The ones that tried, stopped. Make more persuasive arguments. It's not my fault, or the result of a message board popularity contest, that anyone can simply look at a list of the most popular and important sites on the Internet and see that virtually none of them are DNSSEC-signed, or observe that it's been 25 years of standardization effort with DNSSEC to no avail, or to poke around in their browser, the most important piece of Internet software they run, and see that it has no support for DNSSEC, or find articles from the TLS architects of browsers explaining why they can't get DANE to work. Those are just facts. They're not personal attacks on you. ps Here's a link from another person who doesn't want to wade into the orange site to make a point, about LetsEncrypt doing multi-perspective lookups, which protect DV challenges from spoofing and, of course, do not rely on DNSSEC, which nobody uses: https://community.letsencrypt.org/t/acme-v1-v2-validating-challenges-from-multiple-network-vantage-points/112253 https://community.letsencrypt.org/t/acme-v1-v2-validating-ch... pps If ISRG is so bought into DNSSEC, why isn't LetsEncrypt.org signed?
- tialaramex 7y ago> Since browsers are the only important customer of DANE, it's funny to see them referred to as "the anti-DANE lobby". In the context that's exactly what they are? DANE proponents securing server-to-server email wanted to have an HSTS-style flag for TLS so they could use it for "OK this server says it always does DANE, if I try to connect in future and can't get DANE that's an attack, I'll just spool the mail". They wrote a simple draft which was then proposed for adoption by the working group. The honest thing for the anti-DANE lobby to do was reject adoption. The draft could proceed as an independent submission and live or die on its own. But instead tactically browser vendor participants supported adoption, and then stalled the process asking for endless tweaks and extra stuff even though they had no intention to deploy it. Basically they ensured it wouldn't get finished and adopted in a timely fashion. AIUI Kathleen chewed people out for abuse of process, everybody was very contrite but the harm can't be undone.
- tptacek 7y agoYou're talking about chain-extensions? Can you address anything I actually said? That all the browser developers as a bloc will pressure standards groups not to make more DNSSEC happen is not something I'm interested in litigating. Since they're the model consumers of DANE, it's weird to refer to them as a lobby; it's like talking about "the user lobby". It's a semantic point and not an important one, so I'm fine to stipulate that "almost everyone who will ever have to deal with DANE" constitutes "the anti-DANE lobby".
- tialaramex 7y ago> Can you address anything I actually said? Here? Or in the Twitter thread where for some reason rather than quote what I wrote you decided to make stuff up about me claiming Let's Encrypt loves DNSSEC ? Let's try this: > it doesn't matter, because nobody signs their zones. Last century when I spent a lot of my spare time working on a vanity site with friends that site didn't have HTTPS. These days the same site (now mostly historical) does have HTTPS. Did HTTPS not matter last century? Did it start mattering? When and how did that happen? No, HTTPS mattered all along but ordinary people don't really prioritise security. It's a long way behind like dental hygiene and remembering grandma's birthday, and like those it'll only get done if it's made as convenient as possible. So that's what we have to do. Well, that's what we should be doing. Instead you're arguing for the status quo for the past half a decade or so. > That all the browser developers as a bloc will pressure standards groups not to make more DNSSEC happen is not something I'm interested in litigating DANE was undeployable. But what they learned with TLS 1.3 was that if something is undeployable (originally TLS 1.3 was undeployable) you can fix that through a mixture of encrypting more things and lying to middleboxes. So that's what you should be expecting. The future isn't a closed web where everything is just Facebook posts but to a middlebox it may look that way because it turns out that middleboxes allow Facebook posts unmolested (People who sign off on buying a middlebox don't know what TCP/IP is but they use Facebook and they'll be angry if it stops working) and so it's easier to just disguise say a DNS request as a Facebook post and then unwrap and decrypt it at the destination. Only half joking.
- dang 7y agoPlease don't break the site guidelines like your comment did here with those first and last bits. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html It's a pity you posted that way, because users flagged it, which eventually removed it from view. That makes sense, because protecting the container here (the commons—not any one user) is more important. But it's a pity because it takes your argument out of the mix. Even if users hadn't flagged it, crossing into snark/flamewar/personal attack discredits your points anyway, so please don't do that. I know nothing about the issue here, but it seems to me that if your post had begun at "Let's Encrypt obeys the ACME RFC" and ended at "for the same reason", it would have been fine for HN. (If you care, you'd be welcome to email hn@ycombinator.com and we could let you edit the post.)