Re: [Suit] Common firmware update flaws

Fabien BESSIERES <bessieres.fabien@gmail.com> Thu, 17 September 2020 18:01 UTC

Return-Path: <bessieres.fabien@gmail.com>
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 D63453A0EE2 for <suit@ietfa.amsl.com>; Thu, 17 Sep 2020 11:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 bWBErtaW9Fkr for <suit@ietfa.amsl.com>; Thu, 17 Sep 2020 11:01:43 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D764D3A0CAF for <suit@ietf.org>; Thu, 17 Sep 2020 11:01:42 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id d15so3153876lfq.11 for <suit@ietf.org>; Thu, 17 Sep 2020 11:01:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Tnh5Bd+TJ2WjK/JWZW5IYK5Kda0+ev8Ir/9Qo0LA/3w=; b=BUctk5NL1Nwu4t2QO7qSNkvoFcGYasceRFQT1pmy25VOuzSpOqQbWCMZ5GuhY0LveW keSZsQBSDy8SAsS3pnySanKKhEUSPOXihByXWHbGHN5zcf8/TkhcrMpNY8d7AhM5NrX0 6lvxnGdzXgnfQoYu4eb+93a69JtBO7pErZDz4LFaWRAQbZthM9b/fUAbQdAKvR7lWoPi 0kP61IYq/5RS0WqHbtAYYplvDOhRfEVh+R0zlRn+a+LKPOW8WbOVhUiXu7ivDLallDew o+MfTMVj2VfBDyi21aC04g2At5Sz24DRJjzvrG7VTPO9gY3qTnA/2OvbfyB6r9/COfPk k8ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Tnh5Bd+TJ2WjK/JWZW5IYK5Kda0+ev8Ir/9Qo0LA/3w=; b=T1Jul2Vph1gxqL4D+QMZRrYEZfZnjRWo7N7AP2QAiqn8lcIb+MljKF6brlWnhrw03m +ryTBbvWiFoIk1qfBrXoP6TgKrDWGU1uS+iO9IphBvsvAddFX2IDNABT4cXe4JUkbbuu HNCwJDli0+0g/uL6TqtI40pu2Lz3e3wrM7E9LWzj2u/fjLshmdmm4+9ntLNpRK+8CjR6 NefvmaoCbmj8ilAaMaeaxXFcleLRTQtxqCPoPLqObzHe8KG0y6j8aBLltc3Rzgn4PCa8 sZyY63Jlq0Yctm58DD0FUHUV+RWYnfUrv6vJ4dtZAzL1y2ViJgbmMBDNA0LyxQYfFG8t DxWQ==
X-Gm-Message-State: AOAM532S0VckUaKsWSyf1AQ9j3qBL4Tce0IY3CKkAd5Hw8FuJosvhrZO CdsoxjPaYLjucu+WJYmquoISivH3hhRXdgEOwAtFIz8JNWI=
X-Google-Smtp-Source: ABdhPJw8n5ayj3XNpwtjP222DgZ09QVBHdZ0PF6EDFA4yweRPAUehFJjCRveJdpXwO5LwJPAH1hKOWpeOwq6mV0srMo=
X-Received: by 2002:a19:9141:: with SMTP id y1mr8876410lfj.554.1600365700964; Thu, 17 Sep 2020 11:01:40 -0700 (PDT)
MIME-Version: 1.0
References: <AM0PR08MB3716F68A9DD2AC86EE540710FA3E0@AM0PR08MB3716.eurprd08.prod.outlook.com>
In-Reply-To: <AM0PR08MB3716F68A9DD2AC86EE540710FA3E0@AM0PR08MB3716.eurprd08.prod.outlook.com>
From: Fabien BESSIERES <bessieres.fabien@gmail.com>
Date: Thu, 17 Sep 2020 20:01:32 +0200
Message-ID: <CAGpCU7GWRO=-c4SZb=Xt96ARjmZr4=LoLRWr0d3JfAMXG5D5rA@mail.gmail.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: suit <suit@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001de3dd05af862d07"
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/_9UYhRtmyqfI_UB2BtSCtiqv0Vg>
Subject: Re: [Suit] Common firmware update flaws
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 17 Sep 2020 18:01:45 -0000

Hi,

Here is my feedback :

Question 1: I believe that the architecture document could include a list
of common practices that are insecure.

Question 2: (a) I don't see any problem in adding directly referenced to
published flaws.
(b) But yes it should be examples that are fixed with the SUIT manifest

I believe that addressing common mistakes/errors/flaws is one of the goals
of the architecture, so it should appear in the document. What do you think
?

Fabien

Le jeu. 17 sept. 2020 à 08:58, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
a écrit :

> Hi all,
>
>
>
> In his review, Bob Briscoe suggested to list “common practices that are
> insecure, and perhaps some common misconceptions about secure firmware
> update” in the SUIT architecture document.
>
>
>
> So far, nobody suggested to include such a list in the architecture
> document and hence I would like to reach out to the group.
>
>
>
> There are different ways to write such a text and the key decisions are:
>
>
>
>    1. Should we include references to published flaws or keep the
>    description abstract?
>    2. Should we include only examples that we later fix with the SUIT
>    manifest? For example, a firmware update can change the nature of a product
>    (e.g. excluding the use of third party printer cartridges).
>
>
>
> Question 1: Would you like to have such text to be added?
>
>
>
> Question 2: If so, what is your answer to (a) and (b)?
>
>
>
> Your feedback is appreciated. Text contributtions are welcome!
>
>
>
> Ciao
>
> Hannes
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> _______________________________________________
> Suit mailing list
> Suit@ietf.org
> https://www.ietf.org/mailman/listinfo/suit
>