4 ms·
In summation, you propose a forklift upgrade of the DNS requiring hundreds of millions of dollars of effort from operators around the world, introducing a syste
by tptacek 1y ago
In summation, you propose a forklift upgrade of the DNS requiring hundreds of millions of dollars of effort from operators around the world, introducing a system that routinely takes some of the most sophisticated platforms off the Internet entirely when its brittle configuration breaks, to address the problem of someone pulling off a global hijack of all the Route53 addresses.
At this point, you might as well just have the CABForum come up with a new blessed verification method based on RDAP. That might actually happen, unlike DNSSEC, which will not. DNSSEC has lost signed zones in North America over some recent intervals.
I do like that the threat model you propose is coherent only for sites behind Cloudflare, though.
- iscoelho 1y ago"I do like that the threat model you propose is coherent only for sites behind Cloudflare, though." The threat model I proposed is coherent for Cloudflare because they have done a lot of engineering to make it almost impossible to globally BGP hijack their IPs. This makes the multi-perspective validation actually help. Yes, other ISPs are much more vulnerable than Cloudflare, is there a point? You are not saying DNSSEC doesn't serve a real purpose. You are saying it is annoying to implement and not widely deployed as such. That alone makes me believe your argument is a bit dishonest and I will abstain from additional discussion.
- tptacek 1y agoNo, I'm saying it doesn't serve a real purpose. I've spent 30 years doing security work professionally and one of the basic things I've come to understand is that security is at bottom an economic problem. The job of the defender is to asymmetrically raise costs for attackers. Look at how DNS zones and certificates are hijacked today. You are proposing to drastically raise defender costs in a way that doesn't significantly alter attacker costs, because they aren't in the main using the exotic attack you're fixated on. If we really wanted to address this particular attack vector in a decisive way, we'd move away, at the CA level, from relying on the DNS protocol browsers use to look up hostnames altogether, and replace it with direct attestation from registrars, which could be made _arbitrarily_ secure without the weird gesticulations DNSSEC makes to simultaneously serve mass lookups from browsers and this CA use case. But this isn't about real threat models. It's about a tiny minority of technologists having a parasocial relationship with an obsolete protocol.
- iscoelho 1y ago[flagged]
- tptacek 1y agoAre you claiming that most DNS zone hijacks occur because an on-path attacker intercepts and spoofs replies to DNS queries? That's not the case.
- iscoelho 1y agoI never said "most". I said it happens and is documented.
- tptacek 1y agoI'm pretty satisfied with how this part of the thread represents this part of my argument.
- deknos 1y agoyeah, the same for the rest. your fanboys are happy and the rest is just tired, because everyone who does not share your point of view has a invalid opinion.
- growse 1y agoWe could live in a world where they don't exist and the vast majority of major financial institutions still wouldn't implement DNSSEC. https://dnsinstitute.com/research/2020/banks-dnssec-202010.html https://dnsinstitute.com/research/2020/banks-dnssec-202010.h... You don't have to like, or agree with anyone. The data tells its own story.
- tigerente 1y agoWhat would be the most common method of DNS zone hijacks, Kaminsky attacks?