Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID check

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 05 April 2020 20:51 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC0613A0D11 for <iot-onboarding@ietfa.amsl.com>; Sun, 5 Apr 2020 13:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] 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 c9LUIzcCeykD for <iot-onboarding@ietfa.amsl.com>; Sun, 5 Apr 2020 13:51:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13BAD3A0D0E for <iot-onboarding@ietf.org>; Sun, 5 Apr 2020 13:51:32 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 4E0F73897C; Sun, 5 Apr 2020 16:49:51 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EB77B72E; Sun, 5 Apr 2020 16:51:24 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "M. Ranganathan" <mranga@gmail.com>, Dan Harkins <dharkins@lounge.org>, iot-onboarding@ietf.org
In-Reply-To: <CAHiu4JNjcaRymun442-vRKXhd-L2W6Jgudkyi5DG8dZjTwzrkw@mail.gmail.com>
References: <CAHiu4JMF22GQBV+yNtN5ySUvJtcc8_+xj9biJLE9Dcc1YvUp9w@mail.gmail.com> <0e3c75ca-52b1-6117-cd5c-0bfe5ba9c381@lounge.org> <CAHiu4JNjcaRymun442-vRKXhd-L2W6Jgudkyi5DG8dZjTwzrkw@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Sun, 05 Apr 2020 16:51:24 -0400
Message-ID: <6001.1586119884@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/ay59jCnL8DV5Vl4xKf23zAM0278>
Subject: Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID check
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IoT onboarding mechanisms <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2020 20:51:37 -0000

    > This check does proof-of-possession of the private key. I think it's
    > very important.

I agree: it matters a lot, but I think more on EST renewal.
We didn't change EST, so really 7030 text should prevail.

It's not always the case that the TLS connection will be originated with
a client certificate identical to the keypair that will be enrolled.

    > Second, what can be done if TLS Unique ID is not supported (e.g. TLS 1.3)?

There is a new channel binding interface, and really there should probably be
an update to use that.

--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-