Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?

Joe Abley <jabley@ca.afilias.info> Fri, 25 July 2008 17:13 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8BCF3A699D; Fri, 25 Jul 2008 10:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level:
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fNtKT8C-T2D9; Fri, 25 Jul 2008 10:13:01 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 828B43A6A65; Fri, 25 Jul 2008 10:13:01 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1KMQhG-000Gbc-Pw for namedroppers-data@psg.com; Fri, 25 Jul 2008 17:03:14 +0000
Received: from [199.212.90.4] (helo=monster.hopcount.ca) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>) id 1KMQhC-000Gaz-OB for namedroppers@ops.ietf.org; Fri, 25 Jul 2008 17:03:12 +0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=monster; d=ca.afilias.info; h=Received:Cc:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer; b=Lc2vuZDmIEQKJct93mjOqC+7mPp+dVi3leFAfFLIk13c1UXK8gI7ry8nnIsCryfulPOYfBZYrVtxQ10i13OLPz5q2KeyxwnQkt4qc66I0IrbRqhQpZJur/KMyP4UIhP7;
Received: from [199.212.90.13] (helo=calamari.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>) id 1KMQh8-0007em-7E; Fri, 25 Jul 2008 17:03:06 +0000
Cc: DNSEXT WG <namedroppers@ops.ietf.org>
Message-Id: <E7388E94-D031-4059-91F9-1596A254E21C@ca.afilias.info>
From: Joe Abley <jabley@ca.afilias.info>
To: Jelte Jansen <jelte@NLnetLabs.nl>
In-Reply-To: <4888FED2.6060204@NLnetLabs.nl>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Subject: Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
Date: Fri, 25 Jul 2008 13:03:05 -0400
References: <48875934.8080101@links.org> <F113C53F-D189-45A0-8DC3-14725395D1BD@virtualized.org> <20080723183227.GA11957@outpost.ds9a.nl> <2FFE6519-7E9C-4DE8-AF69-697A4D875011@nominum.com> <20080723191636.GB32507@outpost.ds9a.nl> <8A91CF57-0CBD-4CF2-BF59-C7D59CB4B7B9@virtualized.org> <20080724060743.GA7420@outpost.ds9a.nl> <48886C4D.4020500@ca.afilias.info> <63C0FFE7-17E6-4ECE-9A12-0537FE2E3F4B@ca.afilias.info> <4888FED2.6060204@NLnetLabs.nl>
X-Mailer: Apple Mail (2.928.1)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>

On 24 Jul 2008, at 18:14, Jelte Jansen wrote:

> how would you verify anything without a trust anchor?

Surely that's a mechanical detail.

> I don't think anyone here implies that DNSSEC works when you do not
> actually turn it on on the resolver you are using.

The implication I was replying to seemed to state fairly clearly that  
DNSSEC would make it impossible for middleboxes to meddle with DNS  
queries and replies and provide answers that were not those that would  
be received from the authority-only servers concerned.

I think that's wrong. I think that once someone is in the position of  
being able to meddle with the query/response stream, all bets are off  
and DNSSEC is no cure.

What is required to circumvent such sabotage is not the ability to  
verify the integrity of the data in-band, but either the ability to  
signal that signatures should be present out-of-band, or a means of  
verifying transport integrity to a resolver which is trusted, or  
something. DNSSEC on its own isn't enough.


Joe


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>