Not logged in
Log in now
Create an account
Subscribe to LWN
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
LWN.net Weekly Edition for May 9, 2013
That sounds a lot like my understanding of what DNSSEC is, or wants to be.
But it doesn't work if you don't have that whole chain of trust going all
the way to the root.
Details of the DNS flaw revealed
Posted Aug 13, 2008 21:29 UTC (Wed) by hmh (subscriber, #3838)
Read up on DNSSEC and look-aside validation.
ISC and friends have worked around the politic crap about signing the root. It is some other
pesky details that are causing issues for DNSSEC deployment.
And server/network performance IS one of them.
Posted Aug 15, 2008 12:00 UTC (Fri) by tialaramex (subscriber, #21167)
The manual steps in DNSSEC deployment mean that even if by some miracle tomorrow the root
servers offered a signed zone and began accepting requests to sign KSKs from the TLDs, it
would be years before the majority of public domains were secured, so the increase in
resources required would be gradual, rather than overnight.
The root server operators seem to have made it plain that for /them/ at least the performance
is not a problem. Several ccTLDs have deployed as islands, so they obviously don't think
performance is a problem.
There is the enumeration problem, but again that doesn't affect the root because its contents
are public. Some ccTLDs have said that they don't believe this is a problem for them either,
because local regulations mean the list of domains and registrants is public anyway. And even
for some of the domains where enumeration isn't acceptable, there are solutions to deploy
today if the will existed, and better solutions on the horizon.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds