Re: [Suit] suit-firmware-encryption-00

Laurence Lundblade <lgl@island-resort.com> Thu, 27 May 2021 20:02 UTC

Return-Path: <lgl@island-resort.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 6AE603A0CB4 for <suit@ietfa.amsl.com>; Thu, 27 May 2021 13:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 hGIwUwEOHEri for <suit@ietfa.amsl.com>; Thu, 27 May 2021 13:02:04 -0700 (PDT)
Received: from p3plsmtpa07-02.prod.phx3.secureserver.net (p3plsmtpa07-02.prod.phx3.secureserver.net [173.201.192.231]) (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 8E2553A0CB2 for <suit@ietf.org>; Thu, 27 May 2021 13:02:04 -0700 (PDT)
Received: from laurences-mbp.lan ([66.75.226.193]) by :SMTPAUTH: with ESMTPSA id mMCclokJG8OT7mMCelvGzA; Thu, 27 May 2021 13:02:01 -0700
X-CMAE-Analysis: v=2.4 cv=Jro0EO0C c=1 sm=1 tr=0 ts=60affaba a=OzioJMgUBeUwR0bSiUZaCA==:117 a=OzioJMgUBeUwR0bSiUZaCA==:17 a=IkcTkHD0fZMA:10 a=gKmFwSsBAAAA:8 a=tGX7uwomAAAA:8 a=Eql3ik4PkCph1paKBf4A:9 a=QEXdDO2ut3YA:10 a=nnPW6aIcBuj1ljLj_o6Q:22 a=ZFOOzkjxzLGrPE5HuMia:22
X-SECURESERVER-ACCT: lgl@island-resort.com
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Laurence Lundblade <lgl@island-resort.com>
In-Reply-To: <609DDBA2-DB43-46C6-85C4-D91DD08D689C@tzi.org>
Date: Thu, 27 May 2021 13:01:58 -0700
Cc: Russ Housley <housley@vigilsec.com>, Michael Richardson <mcr+ietf@sandelman.ca>, suit@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F683414D-2C37-44D5-947A-4E8FD969DCB0@island-resort.com>
References: <19586.1622075797@localhost> <2A8B7C9F-487D-4F90-A3BC-DF2FC3C4D21D@vigilsec.com> <609DDBA2-DB43-46C6-85C4-D91DD08D689C@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-CMAE-Envelope: MS4xfJ7YWEGT5idWYrmxset3rsEcsHA/otxMAcmnUJ64xRC949tzJ1OIkeVCMAUXT9tS/Q/YC0mZ6IEpYkE7vGpQd0O63odEpIqFWwGPfENGRRlIYBKb73/u soBpPZ7LjFoIQe7UQj8t2UY4F7TrvFOKMRkiBNy3/N3EPmr8+ODSo2My0XXLeY5WMixRt8ciFssRSQYlSJW4K8quvkIqmWl2IQyx2rNrwNsahQQR+0Z5uROi nkdoiJbV+qLUS1hQUYDIlY/f//fVcaZra7bvOmu4WTY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/xdWZ1qvwcLt9bkRwHXSAKeGTqKY>
Subject: Re: [Suit] suit-firmware-encryption-00
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, 27 May 2021 20:02:09 -0000


> On May 27, 2021, at 12:57 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> On 2021-05-27, at 21:40, Russ Housley <housley@vigilsec.com> wrote:
>> 
>> CEK = content-encryption key, which is defined in PKCS#7 and CMS.  I think the first uses are in RFC 2630 and RFC 2631.
>> 
>> KEK - key-encryption key, which is used in thoses same RFCs, but it was also used as early as RFC 1949.
> 
> FYI: RFC 4949, which should still be the goto resource here, has KEK, but not CEK (which is called a DEK there, if I get the analogy right — I certainly have heard CEK much more than DEK).

COSE RFC 8152 uses CEK and KEK.  I’ve heard them in other contexts and I find them clear and useful myself.

LL