Re: [jose] [COSE] JOSE-HPKE ... was Re: FW: New Version Notification for draft-rha-jose-hpke-encrypt-00.txt

Ilari Liusvaara <ilariliusvaara@welho.com> Thu, 12 October 2023 16:19 UTC

Return-Path: <ilariliusvaara@welho.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91745C1705FD; Thu, 12 Oct 2023 09:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 Du33xet1WyrY; Thu, 12 Oct 2023 09:19:41 -0700 (PDT)
Received: from welho-filter2.welho.com (welho-filter2b.welho.com [83.102.41.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E502C1516E1; Thu, 12 Oct 2023 09:19:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by welho-filter2.welho.com (Postfix) with ESMTP id 376CB46DF2; Thu, 12 Oct 2023 19:19:38 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp2.welho.com ([IPv6:::ffff:83.102.41.85]) by localhost (welho-filter2.welho.com [::ffff:83.102.41.24]) (amavisd-new, port 10024) with ESMTP id 5fowiKUnvwgO; Thu, 12 Oct 2023 19:19:37 +0300 (EEST)
Received: from LK-Perkele-VII2 (78-27-96-203.bb.dnainternet.fi [78.27.96.203]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp2.welho.com (Postfix) with ESMTPSA id AC1B028A; Thu, 12 Oct 2023 19:19:35 +0300 (EEST)
Date: Thu, 12 Oct 2023 19:19:35 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: "jose@ietf.org" <jose@ietf.org>, "cose@ietf.org" <cose@ietf.org>
Message-ID: <ZSgcl6e9aLAZIucn@LK-Perkele-VII2.locald>
References: <169711490018.57213.16557149243913712562@ietfa.amsl.com> <AM0PR07MB5764AB57C67F9AD7849CE87FF4D3A@AM0PR07MB5764.eurprd07.prod.outlook.com> <83500115-5acb-44b5-ad06-21320600de16@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <83500115-5acb-44b5-ad06-21320600de16@gmx.net>
Sender: ilariliusvaara@welho.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/k0NQb922YwXQyKhfm817Qr3aG7o>
Subject: Re: [jose] [COSE] JOSE-HPKE ... was Re: FW: New Version Notification for draft-rha-jose-hpke-encrypt-00.txt
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Oct 2023 16:19:46 -0000

On Thu, Oct 12, 2023 at 05:30:06PM +0200, Hannes Tschofenig wrote:
> Hi all,
> 
> As you may know, we have been working for quite a while on the
> COSE-HPKE specification, see
> https://datatracker.ietf.org/doc/draft-ietf-cose-hpke/. After a lot
> of discussions we managed to make fundamental design decisions
> recently. During those discussions we also talked about the mapping
> of HPKE to JOSE and we learned (off-list) about implementation work.
>
> I believe it is good to have a JOSE-based version of HPKE that aligns
> with the work done in COSE. (It is a -00 version and details will
> change.) I could imagine that many of you will agree with me.

One trap is that while JOSE can align with the two-layer COSE
construction, it can not align with the one-layer COSE construction.
In COSE, the two are linked by duality, but no analogous duality
exists in JWE.

Instead, JOSE requires different mechanism, using HPKE secret export,
which is very similar to  how ECDH direct key agreement works in JOSE.




-Ilari