Re: [Asrg] DNSSEC is NOT secure end to end

David Wilson <David.Wilson@isode.com> Tue, 09 June 2009 08:05 UTC

Return-Path: <David.Wilson@isode.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 4A9863A6925 for <asrg@core3.amsl.com>; Tue, 9 Jun 2009 01:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 5ZniZ4-uFW5u for <asrg@core3.amsl.com>; Tue, 9 Jun 2009 01:05:19 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 396A23A68E1 for <asrg@irtf.org>; Tue, 9 Jun 2009 01:05:19 -0700 (PDT)
Received: from [192.168.50.2] (82-44-14-207.cable.ubr04.mort.blueyonder.co.uk [82.44.14.207]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <Si4XwAAh5Ajp@rufus.isode.com>; Tue, 9 Jun 2009 09:05:24 +0100
From: David Wilson <David.Wilson@isode.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4A2DA4C8.2000304@necom830.hpcl.titech.ac.jp>
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> <1244061519.2778.62.camel@bravo.isode.net> <4A29EC02.6000807@necom830.hpcl.titech.ac.jp> <1244490849.2822.21.camel@bravo.isode.net> <4A2DA4C8.2000304@necom830.hpcl.titech.ac.jp>
Organization: Isode Limited
Date: Tue, 09 Jun 2009 09:05:15 +0100
Message-Id: <1244534715.2760.51.camel@bravo.isode.net>
X-Mailer: Evolution 2.26.2 (2.26.2-1.fc11)
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: Anti-Spam Research Group - IRTF <asrg@irtf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Asrg] DNSSEC is NOT secure end to end
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, 09 Jun 2009 08:05:20 -0000

On Tue, 2009-06-09 at 08:54 +0900, Masataka Ohta wrote:
> > DNSSEC provides two things. Firstly, it provides the means to
> digitally
> > sign RRsets. This provides data origin authentication and data
> > integrity.
> 
> The provision is through hops of certificate authorities,

As I clearly stated, the actual signing is end to end, and if the
receiver has chosen to trust the explicit key used to sign, there is no
involvement of PKI. The presence of a valid digital signature is good
evidence that the data originated in that form from the owner of the
private key corresponding to the public key used for verification.

> which is what is discussed in latter paper of David Clark published in
> 2001. Read it.

I have, and I cannot find any explicit sentence which uses the phrase
"hops of certificate authorities". Nor can I find any statement which
states anything to the effect "PKI is not end to end and is therefore
bad". If these are present, please point them out. He does state "Each
interaction is nominally ... but its robustness depends on the larger
context composed of the whole sequence."

It does state, in effect, "PKI is difficult" (particularly because of
the revocation problem) but that is well known. But it also gives me the
impression that it says that this kind of thing is necessary, because of
the trust issue on the modern Internet.

I'm not sure of the reason for your insisting that DNSSEC is not end to
end.

I must apologise to the Asrg list for continuing this discussion, which
seems to have just gone down a pointless semantic hole.