Re: [Full-disclosure] DNS Cache Dan Kamikaze (Actual Exploit Discussion)




--On July 16, 2008 11:17:07 AM +1000 Mark Andrews <Mark_Andrews@xxxxxxx>=20
wrote:

The real problem isn't signing or resigning zones, or even
successfully=3D20 completing the original configuration (although those
are not trivial for=3D20 the average person trying to setup their own
dns). It's the trust=3D20 anchors. Until the root is signed, trust
anchors are a PITA. And until=3D20 the root is signed, why should =
anyone
believe that DNSSEC will achieve=3D20 wide adoption?

Well there are a number of ccTLD's that are already signed.
RIPE sign their part of the reverse space. ORG is in the
process of getting signed. It's happening.

There are existing solutions to dealing with lack of support
in the infrastructure zones (includes the root). You let
someone you trust collect the trust anchors for you then
incorporate them on a regular basis.

We effectively do this everyday with https but for some
reason people are scared to do the same thing with dns
despite private parts of the keys never being available to
the entity doing the certification. With https the certifying
authority can spoof any site they certify.


Perhaps that's because a cert problem on a web server breaks a single=20
webserver. A cert problem with dns breaks an entire domain.

And a signed root changes that how? You either add your
trust anchor to a reposititory or to the parent zone. You
still need to re-sign regularly. You still have the same
amount of communication to do when you roll over your keys.

B.T.W. DNSSEC problems are easier to chase down than a
broken delegation. I've done both. Neither requires more
than "dig" and "date".

If you are really worried about validation failing you can
always disable it but please sign the zones so that those
of us who would like to be able to use DNSSEC to validate
DNS data have something to work with.

Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@xxxxxxx

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/



Relevant Pages

  • Re: [Full-disclosure] DNS Cache Dan Kamikaze (Actual Exploit Discussion)
    ... the average person trying to setup their own dns). ... Until the root is signed, trust anchors are a PITA. ... the entity doing the certification. ...
    (Full-Disclosure)
  • Re: Event ID 7062 in DNS logs
    ... you advice me to let the default Internet root ... > hints in place and to use forwarders from the child DNS (DNS server in ... > the root DNS (DNS server on the forest root domain hosting the ... > AD-integrated forestroot.com zone). ...
    (microsoft.public.windows.server.dns)
  • Re: AD Login
    ... phyically in the root domain), logon to with their own AD credentials. ... DNS issues OR to firewall/routing issues. ... or perhaps the DNS servers for one domain cannot find the "other" ...
    (microsoft.public.windows.server.active_directory)
  • Re: What is CACHE.DNS file?
    ... By default, when DNS is running on a Windows 2000 domain controller, the ... root hints are read from Active Directory upon startup first. ... Does the above apply to Windows Server 2003 R2 configured as an AD ...
    (microsoft.public.windows.server.dns)
  • Re: Question re: DNS forwarding best practices
    ... change rate of the root DNS zone's content. ... to a primary of the zone, so hopefully you have at least one ... as the case might allow) to the DNS servers of the root. ...
    (microsoft.public.windows.server.dns)