3 ms·
This is really a design flaw in DNSSEC itself. It isn't so much a "vulnerability" in any particular software. BIND and Unbound, and subsequently everyone else
by 1vuio0pswjnm7 3y ago
This is really a design flaw in DNSSEC itself. It isn't so much a "vulnerability" in any particular software. BIND and Unbound, and subsequently everyone else that follows internet trends, intentionally added DNSSEC support even though DNSSEC was flawed from the outset.
Why was DNSSEC revived from the RFC graveyard^1 and implemented by authors of BIND and Unbound. Cache poisoning. Why does cache poisoning exist. Because people use third party shared caches. Why do people use third party shared caches. That one I will leave for the reader.
There are other, varied options. I use stored DNS data from a variety of sources that I can cross-check against each other. I use iterative resolution instead of recursive. I am happy to discover when websites occasionally change their IP addresses. I want to know. But most websites I visit keep the same addresses for years.
Almost all DNS lookups I do are _not_ on a "phone". The number of IP addresses I need for the "phone" is relatively small.
1. According to djb, DNSSEC was first conceived in 1993. And the charlatans behind it started taking money from the USG sometime in or after 1994.
https://cr.yp.to/talks/2009.10.30/slides.pdf https://cr.yp.to/talks/2009.10.30/slides.pdf
That is a long time to be awaiting release in some version of BIND. Gee, I wonder why. With this "KeyTrap" demonstration, one might guess that DNSSEC sat around for 15 years because it was never ready for prime time. One might even conclude it still isn't.
- tptacek 3y agoDNSSEC hasn't been adopted at all, and was designed before the first cache poisoning attacks (both the bailiwick-style extra-records attack and the XID prediction attack, which were exploited separately from 1996 through 1997; Kaminsky's attack that combined the two wouldn't come out for another decade). It isn't motivated by any real threat model, but rather by a DoD effort to synergize all the Internet protocols with IPSEC.