Re: [Asrg] DNSSEC is NOT secure end to end (more tutorial than debating)

Thierry Moreau <thierry.moreau@connotech.com> Tue, 02 June 2009 15:10 UTC

Return-Path: <thierry.moreau@connotech.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBC7128C19B for <asrg@core3.amsl.com>; Tue, 2 Jun 2009 08:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599]
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 Uj0JkkL7uQuF for <asrg@core3.amsl.com>; Tue, 2 Jun 2009 08:10:14 -0700 (PDT)
Received: from smtp113.rog.mail.re2.yahoo.com (smtp113.rog.mail.re2.yahoo.com [68.142.225.229]) by core3.amsl.com (Postfix) with SMTP id DCB2628C0F5 for <asrg@irtf.org>; Tue, 2 Jun 2009 08:10:13 -0700 (PDT)
Received: (qmail 83463 invoked from network); 2 Jun 2009 15:10:13 -0000
Received: from unknown (HELO connotech.com) (thierry.moreau@209.148.165.15 with plain) by smtp113.rog.mail.re2.yahoo.com with SMTP; 2 Jun 2009 15:10:13 -0000
X-YMail-OSG: CB9n7ugVM1kW_DZw4NzWQPgWb4HhfZ8jd9rAcfF897xfoDgedOBQg3pTwLlFwnxqow--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4A25404E.1080601@connotech.com>
Date: Tue, 02 Jun 2009 10:07:58 -0500
From: Thierry Moreau <thierry.moreau@connotech.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>
References: <200905302032.n4UKVxaZ048822@givry.fdupont.fr> <4A21C0CB.8070409@necom830.hpcl.titech.ac.jp> <8EFB68EAE061884A8517F2A755E8B60A1EF83F8661@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <4A252B54.6020508@necom830.hpcl.titech.ac.jp> <4A2533B3.7070804@bbn.com>
In-Reply-To: <4A2533B3.7070804@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 02 Jun 2009 10:34:15 -0700
Cc: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, Christian Huitema <huitema@windows.microsoft.com>, Francis Dupont <Francis.Dupont@fdupont.fr>, "ietf@ietf.org" <ietf@ietf.org>, Anti-Spam Research Group - IRTF <asrg@irtf.org>
Subject: Re: [Asrg] DNSSEC is NOT secure end to end (more tutorial than debating)
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2009 15:10:16 -0000

Richard Barnes wrote:

> This debate has nothing to do with the security properties of DNSSEC.
> 
> A basic assumption of the DNS is that what the authoritative server for 
> zone says is, well, authoritative.  The structure of DNS itself entitles 
> JPNIC to point ac.jp wherever they want; by using a name within the .jp 
> domain, you are agreeing to act within JPNIC's domain of control.  JPNIC 
> could set up an authoritative server for hpcl.titech.ac.jp completely 
> independently of you, regardless of DNSSEC, and from the perspective of 
> the DNS, that would be the right answer.
> 

I guess what Masataka was referring to is a different source of 
variance, i.e. an impersonation of JPNIC's authority over its domain of 
control (using a compromised JPNIC's private key).

> All DNSSEC does is make the assertions made in the DNS reliable -- it 
> does nothing to change the locus of control.
> 

Reliable through a chain fo digital signatures. Reliable to the extent 
an impersonation attack (on the locus of control) does not occur based 
on a compromised private signature key.

> On the other hand, you can certainly use the DNSSEC protocol elements to 
> do peer-to-peer security, just like you can use private DNS servers, and 
> just like you can use TLS without trust anchors (i.e., with self-signed 
> certs).  Just hand out the public half of your ZSK to people you want to 
> be able to verify names within your zone.
> 

Then you reduce the chain of digital signatures to a single one, raising 
confidence level at the cost of more key management hindrance.

Indeed, this thread seems to be another attempt to understand the basic 
DNSSEC properties.

- Thierry

> --Richard
>