Re: [Fud] Constrained Firmware update challenge
Carsten Bormann <cabo@tzi.org> Mon, 17 April 2017 17:01 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: fud@ietfa.amsl.com
Delivered-To: fud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15CDA126C2F for <fud@ietfa.amsl.com>; Mon, 17 Apr 2017 10:01:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 NyXQhhAs-jU7 for <fud@ietfa.amsl.com>; Mon, 17 Apr 2017 10:01:52 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 D78F213169E for <fud@ietf.org>; Mon, 17 Apr 2017 10:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3HH1g0C022983; Mon, 17 Apr 2017 19:01:42 +0200 (CEST)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3w6F0k0TXqzDHWV; Mon, 17 Apr 2017 19:01:42 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <3324.1492442781@obiwan.sandelman.ca>
Date: Mon, 17 Apr 2017 19:01:41 +0200
Cc: fud@ietf.org
X-Mao-Original-Outgoing-Id: 514141300.931397-7845dd6e1d9743e681bfd8a5ebd8c900
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F5AB023-888C-49E2-B857-5CB65EACA261@tzi.org>
References: <1980.1492374868@obiwan.sandelman.ca> <E3933EC6-88AD-4754-9FC1-98F55B6755FC@tzi.org> <3324.1492442781@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/4q7IhbWc_uowQYlb5ZQYOcY5rdM>
Subject: Re: [Fud] Constrained Firmware update challenge
X-BeenThere: fud@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: FUD - Firmware Updating Description <fud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fud>, <mailto:fud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/fud/>
List-Post: <mailto:fud@ietf.org>
List-Help: <mailto:fud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fud>, <mailto:fud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Apr 2017 17:01:54 -0000
> On Apr 17, 2017, at 17:26, Michael Richardson <mcr+ietf@sandelman.ca> wrote: > > Updates may be impossible > (burnt into ROM), Too much code for my taste (and much of this is security relevant, so it probably needs updates at some point). > or it might just be a special part of the flash that > is seperate from the main code. More likely, and more likely that you’d keep two copies of that, so you can upgrade the bootloader itself. (Needs jump tables if that massive amount of code also needs to be reused by the application.) Grüße, Carsten
- [Fud] Constrained Firmware update challenge Michael Richardson
- Re: [Fud] Constrained Firmware update challenge Carsten Bormann
- Re: [Fud] Constrained Firmware update challenge Michael Richardson
- Re: [Fud] Constrained Firmware update challenge Carsten Bormann
- Re: [Fud] Constrained Firmware update challenge Michael Richardson