Re: [DNSOP] On trust anchors, roots of trust, humans and indirection

Paul Vixie <paul@redbarn.org> Sun, 01 April 2018 01:53 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BEF01200FC for <dnsop@ietfa.amsl.com>; Sat, 31 Mar 2018 18:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7s_6jtu-ZwY9 for <dnsop@ietfa.amsl.com>; Sat, 31 Mar 2018 18:53:49 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1FCD1205F0 for <dnsop@ietf.org>; Sat, 31 Mar 2018 18:53:48 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:dd04:78fb:edc1:47b1] (unknown [IPv6:2001:559:8000:c9:dd04:78fb:edc1:47b1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id BCBC47594D; Sun, 1 Apr 2018 01:53:48 +0000 (UTC)
Message-ID: <5AC03BAA.3080601@redbarn.org>
Date: Sat, 31 Mar 2018 18:53:46 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.24 (Windows/20180302)
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
CC: "dnsop@ietf.org" <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Michael StJohns <msj@nthpermutation.com>
References: <a9bd794f-41bc-9593-db0d-5424c84431a3@nthpermutation.com> <alpine.DEB.2.11.1803281105310.10477@grey.csi.cam.ac.uk> <cfc66d01-c8ce-b605-8074-8400b377f414@nthpermutation.com> <alpine.DEB.2.11.1803301403230.25657@grey.csi.cam.ac.uk> <CAMm+Lwj5JwrOTfWqNX740bgRYFn4k7gAhOB=cm=LYed=0Pu9pQ@mail.gmail.com> <alpine.DEB.2.11.1803301700030.30706@grey.csi.cam.ac.uk> <5ABE641F.6020501@redbarn.org> <alpine.DEB.2.11.1803312346270.5300@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.11.1803312346270.5300@grey.csi.cam.ac.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/UCxAWinjY5GKM1Gb3CTs3XwDVmM>
Subject: Re: [DNSOP] On trust anchors, roots of trust, humans and indirection
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Apr 2018 01:53:50 -0000


Tony Finch wrote:
> Paul Vixie<paul@redbarn.org>  wrote:
>> devices which cannot be updated by their makers must expire
>
> Definitely.
>
> I think the problem that most concerns me is the device that spends 3 or 6
> months in a box between manufacturing and deployment, and which expects to
> do a software update when it is plugged in, but there was a DNSSEC root
> key rollover in the intervening time.
>
> At the moment the only solution we can offer is to turn off DNSSEC until
> the device has done enough updating to be able to turn DNSSEC on again.
> Which is to say, DNSSEC is a hindrance not a help. This is an embarrassing
> failure.
>
> ...

i suggest that bind, unbound, powerdns, and so on change their packaging 
to put the trust anchor in a different upgradeable package (.deb, .rpm, 
etc) than the software itself. until and unless the package manager is 
secured by DANE rather than by ssh/pgp/x509/etc, then the solution for 
being on the shelf for several months is, do a software update before 
you try to go online.

it's only a failure if you think should have been trying to do it in the 
first place, and the more i see from 5011 and the sentinel thread, the 
more convinced i am that this should have been put deliberately out of 
scope, many years ago.

-- 
P Vixie