Re: [dnsext] Historical root keys: The Large Router Vendor Speaks

Paul Wouters <paul@xelerance.com> Sat, 29 January 2011 03:10 UTC

Return-Path: <paul@xelerance.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 770D83A6ADE for <dnsext@core3.amsl.com>; Fri, 28 Jan 2011 19:10:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level:
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.023, 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 iActFXo6J2I1 for <dnsext@core3.amsl.com>; Fri, 28 Jan 2011 19:10:53 -0800 (PST)
Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by core3.amsl.com (Postfix) with ESMTP id 2836F3A6ADB for <dnsext@ietf.org>; Fri, 28 Jan 2011 19:10:52 -0800 (PST)
Received: from tla.xelerance.com (tla.xelerance.com [193.110.157.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by newtla.xelerance.com (Postfix) with ESMTP id 6A16CC542 for <dnsext@ietf.org>; Fri, 28 Jan 2011 22:13:59 -0500 (EST)
Date: Fri, 28 Jan 2011 22:13:59 -0500
From: Paul Wouters <paul@xelerance.com>
To: dnsext@ietf.org
In-Reply-To: <alpine.LFD.1.10.1101282140340.32489@newtla.xelerance.com>
Message-ID: <alpine.LFD.1.10.1101282212310.32489@newtla.xelerance.com>
References: <4D41D3E2.6060107@cisco.com> <3125F45F-7594-498F-AFA3-D2D738A228F5@hopcount.ca> <4D42ED13.5030000@cisco.com> <20110128163656.GC30257@shinkuro.com> <AANLkTik4zCA96_vJus5r0HuhpscR4swmnb=y3UFedhWM@mail.gmail.com> <alpine.LFD.1.10.1101282140340.32489@newtla.xelerance.com>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Subject: Re: [dnsext] Historical root keys: The Large Router Vendor Speaks
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jan 2011 03:10:56 -0000

On Fri, 28 Jan 2011, Paul Wouters wrote:

> On Fri, 28 Jan 2011, Phillip Hallam-Baker wrote:
>
>> Beyond that, I do not like the idea of a chain of historical roots. It 
>> means that compromise of any root will poison the ones downstream. There 
>> are five
>> potential points of compromise in the following chain:
>> 
>> A -> B, B->C, C->D, D->E
>> 
>> This approach only ever has two at any given time:
>> 
>> A->B, A->C, A->D, A->E
>
> But that requires the key move somewhere trusted so it can make a NEW
> signature for the A->C transition, after A has been retired for B. Or
> rather, when you deploy E, you have 5 root keys to protect instead of

Oops, as Phillip said, it is only two. I misunderstood. But it still requires
two private root keys to be available, instead of one.

Paul