Re:Dan Kaminsky responds (at length) to DJB's 27C3 DNSSEC pr...
by tptacek on Thursday January 06, 2011 @10:32PM
(#2078443)
The notion of "endpoint validation" has an entirely different meaning in DNSCurve than it does in DNSSEC.
In DNSSEC, all the security resides in the actual DNS records. End-to-end security means verifying each step in the DNS chain, from .org through "www". This is the only way DNSSEC provides any value.
Unlike DNSSEC (shockingly), DNSCurve protects the actual conversation between a name resolver and a name server, irrespective of the RR's configured for a zone. DNSCurve (for the most part) does not care about your RR's. When one speaks of "end-to-end DNSCurve", one is talking about a hypothetical universe in which the root servers all the way down are speaking DNSCurve.
That world is never going to happen.
The point of DNSCurve is that it provides a degree of security --- by my reckoning, the most important degree --- even if the roots don't adopt DNSCurve. And in that universe, caching works just fine: DNSCurve is only going to be used to connect endpoints to caches.
In DNSSEC, all the security resides in the actual DNS records. End-to-end security means verifying each step in the DNS chain, from .org through "www". This is the only way DNSSEC provides any value.
Unlike DNSSEC (shockingly), DNSCurve protects the actual conversation between a name resolver and a name server, irrespective of the RR's configured for a zone. DNSCurve (for the most part) does not care about your RR's. When one speaks of "end-to-end DNSCurve", one is talking about a hypothetical universe in which the root servers all the way down are speaking DNSCurve.
That world is never going to happen.
The point of DNSCurve is that it provides a degree of security --- by my reckoning, the most important degree --- even if the roots don't adopt DNSCurve. And in that universe, caching works just fine: DNSCurve is only going to be used to connect endpoints to caches.