IETF Logo Mail Archive

Re: [Suit] WG: WGLC on draft-ietf-suit-firmware-encryption-14 due on September 11, 2023

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 10 September 2023 22:26 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 332A5C14CF1C; Sun, 10 Sep 2023 15:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h9pKql3Wvs77; Sun, 10 Sep 2023 15:26:39 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB546C14CE4D; Sun, 10 Sep 2023 15:26:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id B363938DC0; Sun, 10 Sep 2023 18:26:37 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id oplOKV3EpPSJ; Sun, 10 Sep 2023 18:26:36 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id C163338DBF; Sun, 10 Sep 2023 18:26:36 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1694384796; bh=FbTRZRApGAWON2Rne8wMaoLrNCTDkuYO2+pAAvgRvH0=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=mM3ZdC+DE6Qb04GKf7XulJJq2/81PwptVINE4jpvRSlI/u3lUgZFizsWVKePeK3Wf AZmI+tlCxKkJqCbNp2+ZRe/8Rbojzf+rbyEzY1KVqPJhK9yov69SaDWqAI6X0VyD4Q nZGF2LQ6lOBoQ3OT3ewDalXXtSYuH9sy8xw8xCksotjeLSHbqmCQDqr97/fbYDVbyw 1KVtfyLB9pwXHSovP4KesUfL0P9a0zqCSP1tqdwVKBsQKBkeT2XWMkCp/mOXfB/i6w Y+IlRh+OEMyMIjLWpdSjhzDtXx69gYtOXg7vVGt+BubfCpC7hU+6Y95rUgBRFbs6oi QAYxpZbwZXhlQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B9A5D44C; Sun, 10 Sep 2023 18:26:36 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
cc: draft-ietf-suit-firmware-encryption@ietf.org, suit@ietf.org
In-Reply-To: <ZPCRK2B3jdaKVq5L@hephaistos.amsuess.com>
References: <MW4PR09MB988694F9A88981948F4290B4F0E0A@MW4PR09MB9886.namprd09.prod.outlook.com> <GV2PR10MB7438E510408D300D5F5D7659EEE6A@GV2PR10MB7438.EURPRD10.PROD.OUTLOOK.COM> <ZPCRK2B3jdaKVq5L@hephaistos.amsuess.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.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-sha512"; protocol="application/pgp-signature"
Date: Sun, 10 Sep 2023 18:26:36 -0400
Message-ID: <25144.1694384796@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/9XFLlLbAla0YSN5beS_v4LLl8-Y>
Subject: Re: [Suit] WG: WGLC on draft-ietf-suit-firmware-encryption-14 due on September 11, 2023
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Sep 2023 22:26:43 -0000

Christian Amsüss <christian@amsuess.com> wrote:
    > * Rolling out personalization data is an interesting use case (which was
    > only touched on lightly as configuration in the manifest format). If
    > this is becoming a serious use case, please consider syncing with
    > ANIMA to find shared guidance on when personalization through ANIMA or
    > SUIT is preferable, or whether commonalities exist that simplify use
    > in overlap areas.

Hmm.
If by ANIMA, you mean BRSKI, then I think that the interesting role is that
the EST/RFC7030 connection can (and many do use it) to deploy device and
application credentials.   This is rather useful to use for encrypting the
personalized data to.

If by ANIMA, you mean GRASP, then maybe you mean:
      * draft-carpenter-anima-grasp-config-00 (expired)
      * draft-ietf-anima-grasp-distribution

The later could actually be used for distribution of the images and
manifests.  I don't think that there is actually that much to coordinate.

    > * I'm low-key disappointed that the two alternatives of section 3
    > (trust-reencryption or use separate manifests) can neither be solved
    > by the mechanisms of SUIT nor those of COSE in a way that doesn't
    > incur extra round-trips. (The need for the extra signature
    > verification is probably inherent). Is there any lesson for future
    > iterations around COSE or SUIT in this?

I don't see these extra round trips myself.

    > * The use of multiple KEKs (bei they KW or DH) only makes sense if KEKs
    > are ever revoked. Otherwise whoever obtains a single device's material

When you say multiple KEKs, do you mean, per-device KEKs?

    > I think that this section will not age well, both because PIC is
    > becoming more usable throughout toolchains, and because the
    > dual-image approach can be adopted.

+1

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email