Re: [COSE] [Rats] RAM requirements for COSE/CWT
Laurence Lundblade <lgl@island-resort.com> Mon, 21 February 2022 16:07 UTC
Return-Path: <lgl@island-resort.com>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id D3C5C3A0D5B
for <cose@ietfa.amsl.com>; Mon, 21 Feb 2022 08:07:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
autolearn=unavailable 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 SgkSse_r1XYv for <cose@ietfa.amsl.com>;
Mon, 21 Feb 2022 08:07:46 -0800 (PST)
Received: from p3plsmtpa11-07.prod.phx3.secureserver.net
(p3plsmtpa11-07.prod.phx3.secureserver.net [68.178.252.108])
(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 7BA7D3A0D4B
for <cose@ietf.org>; Mon, 21 Feb 2022 08:07:46 -0800 (PST)
Received: from [192.168.1.4] ([75.80.148.139]) by :SMTPAUTH: with ESMTPA
id MBE1nHEO7q4GYMBE1nA0pw; Mon, 21 Feb 2022 09:07:45 -0700
X-CMAE-Analysis: v=2.4 cv=et8acqlX c=1 sm=1 tr=0 ts=6213b8d1
a=qS/Wyu6Nw1Yro6yF1S+Djg==:117 a=qS/Wyu6Nw1Yro6yF1S+Djg==:17 a=7CQSdrXTAAAA:8
a=NEAV23lmAAAA:8 a=ftyS4RUHLyCddB3ajs8A:9 a=QEXdDO2ut3YA:10
a=ol3hlKhJKm3kXTNYljoA:9 a=6cgZI0B0R4e0rSw_:21 a=_W_S_7VecoQA:10
a=CjuIK1q_8ugA:10 a=a-qgeE7W1pNrGK8U0ZQC:22
X-SECURESERVER-ACCT: lgl@island-resort.com
From: Laurence Lundblade <lgl@island-resort.com>
Message-Id: <4C7662A8-D79D-42D2-A07C-9819249A459B@island-resort.com>
Content-Type: multipart/alternative;
boundary="Apple-Mail=_A914C03E-7C9E-4D52-ACB6-E4B5C7D54395"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Mon, 21 Feb 2022 08:07:45 -0800
In-Reply-To: <DBBPR08MB5915B874FD16107A7B0105AAFA3A9@DBBPR08MB5915.eurprd08.prod.outlook.com>
Cc: Anders Rundgren <anders.rundgren.net@gmail.com>,
"rats@ietf.org" <rats@ietf.org>, "cose@ietf.org" <cose@ietf.org>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
References: <e8995f0c-ad85-f702-da6b-051ffdc4cb08@gmail.com>
<DBBPR08MB5915B874FD16107A7B0105AAFA3A9@DBBPR08MB5915.eurprd08.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.104.17)
X-CMAE-Envelope: MS4xfNBaxFdM30XoKAm1dbC7VSmUB94eqQpAYpy/yzyKOxnNknYe81U+fC6kjMB6WCe0P+k6Xmwmo2vF1sFyJ/mwk/qrhyOAfFUfryOqeVeZnr/BgD0yklxl
8ecRx6Ow9Pp1Sr0vr6BSxkGMfhcKKDG/KlH3+VrmiHiq1ddpws0lR14eax6mQgN2wz+9NCHWt/qNfBR5aR97Hs2TAU3w1kbveG6+8LXaZ29vsfJSUTbOQ9Qk
/qSjqqSk4VEq2njYp5dMUGTrPWlZWnwTg/Fsc3+ISwicBdwqTbnzB+ij7A7WH89S
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/QfUZmMAWBWpFnVboZYote68eOZw>
Subject: Re: [COSE] [Rats] RAM requirements for COSE/CWT
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>,
<mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>,
<mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2022 16:07:51 -0000
On Feb 21, 2022, at 6:31 AM, Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote: > > I could, however, imagine to write an COSE implementation that does not require the entire CWT be held in RAM since the digital signature just covers the hash of the CWT and you can use a rolling hash. No need to imagine. For signing, t_cose <https://github.com/laurencelundblade/t_cose>allows you to create COSE headers, then CBOR-encode the payload an item at a time and then append the signature. t_cose does require the completed COSE message be in RAM, but not the input payload. LL
- [COSE] RAM requirements for COSE/CWT Anders Rundgren
- Re: [COSE] RAM requirements for COSE/CWT Carsten Bormann
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Hannes Tschofenig
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Laurence Lundblade
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Anders Rundgren
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Carsten Bormann
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Laurence Lundblade
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Anders Rundgren
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Carsten Bormann
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Anders Rundgren
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Carsten Bormann
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Laurence Lundblade
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Carsten Bormann
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Laurence Lundblade
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Carsten Bormann
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Anders Rundgren
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Carsten Bormann
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Anders Rundgren
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Laurence Lundblade
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Carsten Bormann
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Laurence Lundblade
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Michael Richardson
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Laurence Lundblade
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Anders Rundgren
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Laurence Lundblade
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Jeremy O'Donoghue
- Re: [COSE] [Cbor] [Rats] RAM requirements for COS… Carsten Bormann
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Laurence Lundblade
- Re: [COSE] [Rats] RAM requirements for COSE/CWT Anders Rundgren