Re: [saag] post-X509 cryptographic identities

Nico Williams <nico@cryptonector.com> Sat, 15 February 2020 18:48 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 527E812007A for <saag@ietfa.amsl.com>; Sat, 15 Feb 2020 10:48:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
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 2IFyJWKzRaM8 for <saag@ietfa.amsl.com>; Sat, 15 Feb 2020 10:48:39 -0800 (PST)
Received: from fossa.birch.relay.mailchannels.net (fossa.birch.relay.mailchannels.net [23.83.209.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5898F120058 for <saag@ietf.org>; Sat, 15 Feb 2020 10:48:39 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 8DDB11A1B5C; Sat, 15 Feb 2020 18:48:38 +0000 (UTC)
Received: from pdx1-sub0-mail-a92.g.dreamhost.com (100-96-216-4.trex.outbound.svc.cluster.local [100.96.216.4]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id E51F81A11F8; Sat, 15 Feb 2020 18:48:37 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a92.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Sat, 15 Feb 2020 18:48:38 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Snatch-Arch: 768229073f80292b_1581792518355_1155947269
X-MC-Loop-Signature: 1581792518354:3646333047
X-MC-Ingress-Time: 1581792518354
Received: from pdx1-sub0-mail-a92.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a92.g.dreamhost.com (Postfix) with ESMTP id A27F67F159; Sat, 15 Feb 2020 10:48:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=T6JQX+PZlErCSu udmM4TTlnlj58=; b=o0mYJCTPtehvP9uO54XILdL+vmKuHN4Q29BWhYJLHph+5d wSkcXdNYqDDoHeWE1AelN2trpasxfsq+eEwIdvWjo/OmaR4C1cDA6qsbJCjHJ2zr kBWHSZGkSimrbCNyZmcAfmDw2wfoSEV0tP+CAF/A+iEuzRch1k2kYdxiQ2FY0=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a92.g.dreamhost.com (Postfix) with ESMTPSA id 9C7B97F166; Sat, 15 Feb 2020 10:48:30 -0800 (PST)
Date: Sat, 15 Feb 2020 12:48:28 -0600
X-DH-BACKEND: pdx1-sub0-mail-a92
From: Nico Williams <nico@cryptonector.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: saag@ietf.org
Message-ID: <20200215184827.GB18021@localhost>
References: <ac360994-e747-6913-fdc3-19b7db2e00c3@netmagic.com> <3854.1581431519@dooku> <20200213174617.GQ18021@localhost> <18044.1581688781@dooku> <20200214203306.GW18021@localhost> <3586.1581771453@dooku>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <3586.1581771453@dooku>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: 0
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedugedrjedvgdduvddtucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecukfhppedvgedrvdekrddutdekrddukeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomh
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/aPJkoZLZ440M3nMAkeePrKQ8kqk>
Subject: Re: [saag] post-X509 cryptographic identities
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2020 18:48:41 -0000

On Sat, Feb 15, 2020 at 01:57:33PM +0100, Michael Richardson wrote:
> Nico Williams <nico@cryptonector.com> wrote:
>     > Sure, but PKIX let's you have this too: it's just an alternate issuer
>     > (root).
> 
>     > What would SPKI have given us, really?
> 
> No, PKIX does not have an alternate issuer.
> That's outside of the PKIX.  It's another instance of PKIX.

Sounds like a matter definitions.

> What SPKI gives is the alternate roots are explainable and codifiable within
> the system, rather than making it an externality.  

Out of curiosity, why couldn't that have been done with PKIX?

>     > Cross-signing roots ~= a root anyways.
> 
>     > Every country could run its own roots with mostly or entirely the same
>     > contents as all the others.  From a relying party's point of view,
>     > there's a single root, and _that_ is what matters.
> 
> This would almost be the same thing, except for the liability and
> soveignty issue.

Indeed.

>     > (A relying party might need to change root trust anchors when traveling
>     > if they are forced to or want to change roots.)
> 
> Yes, possibly.  It's definitely an open question, and there is a tussle there.

Sure.  At worst the traveler's origin country and destination might have
conflicting requirements and even great firewalls.

>     > Sovereigns always immunize themselves.  You will not be able to sue
>     > your government over attacks on you resulting from your country's ccTLD
>     > private keys being compromised.  At best some may be able to avoid some
>     > losses when their counter-party is also operating in the same country,
>     > but only entities other than their government will be taking the
>     > losses.
> 
> "I relied upon the trust anchor my government provided me, so, your Honour, I
> am not guilty"

I was referring to the government's civil liability.  For an
individual's liability, especially criminal liability, no doubt this is
(would have to be) a defense.