Re: [jose] [COSE] 🔔 WGLC of draft-ietf-cose-webauthn-algorithms

Mike Jones <Michael.Jones@microsoft.com> Tue, 22 October 2019 16:17 UTC

Return-Path: <Michael.Jones@microsoft.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 55A37120913; Tue, 22 Oct 2019 09:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 Nah-Su8W_fTP; Tue, 22 Oct 2019 09:17:40 -0700 (PDT)
Received: from NAM06-DM3-obe.outbound.protection.outlook.com (mail-eopbgr640102.outbound.protection.outlook.com [40.107.64.102]) (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 C04EA120962; Tue, 22 Oct 2019 09:17:17 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FJfE8KT3rnDBcdwaPQvi5gmF4CPPYpbz4iASdqZUZxAdwXW5CsCZ+IVtYVfRFqHSjlx0KkDO4vHybfQe59nCU+XGcgVtalYUPTPrJ7JQVH8nEDbFP18p85r40Of2klmgpuAposjKmJmgJOulzeXEVs7zxepLtNb0VB4/gDMMxLY6t09BdtySdfd0AYKrHibzEXbCQbDGHophLnoQCB/0vXjjy+t1JdVaBadFpK2xyEGw0tvuUXbC5hPwrzrb4XuKbT1lJiXI6ODQc5ULHOAhmBhzwcS4jtztlIjd0ARXXYcYdF/S2oURa3cHtfdxoyK4zpSEyDi1Mdp0UDYEgj9GTg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oDqnN9XKZahDlxSHJKfxS/GfuSjIUZUKZtG2HpWmgXc=; b=gQ+n8rCA3gtHCvLuIxlE8P6Cg+coeXv3Bx6XfqNc7HzKYjt8z+Jo2KbR7JD4XTB6FMb2JhVx0uK+T6cRAOBxdDiuIqCXAO3xDPsNwGCMHI4IQB9XbcrWuFPVaHpvnge56pYNrfNY7F51bYTByUaTDX8vuBQbMnEz02CkXEWxNBL8yFs7Q7OIWzNOUbzAWbBC8mNetIUMK+3AjbnPe2weW04Lx32u25WXXruSJMUc45JZpcnXg4Vya/0tqwA8VTfe/lLQ9DLmonuceuR0ZRIY0L0trkGrtHY6/w/Op6mhKCFjnHj1JxsmI/6h96Cmt8MYwFQX3rEseGtvxjAdDcEGmA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oDqnN9XKZahDlxSHJKfxS/GfuSjIUZUKZtG2HpWmgXc=; b=jY0stw+S680BCj1m7UCZI5TVByfEJV0zcrnGWiFAWd6AWbBdNXTkk3IA34O3lBBz0eHbn+gadVsjhgcaWggYWXuZcVvhaPDnBN43cusuSalrSrfZNZmyT+93jL0VjLJwXXxdSLvIl/8V5rKf6f55Z+9hjiJIIB5N3qzItXrIR1w=
Received: from DM6PR00MB0569.namprd00.prod.outlook.com (20.179.51.12) by DM6PR00MB0521.namprd00.prod.outlook.com (20.178.30.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2424.0; Tue, 22 Oct 2019 16:17:16 +0000
Received: from DM6PR00MB0569.namprd00.prod.outlook.com ([fe80::bd43:8b51:d67d:91e3]) by DM6PR00MB0569.namprd00.prod.outlook.com ([fe80::bd43:8b51:d67d:91e3%3]) with mapi id 15.20.2424.000; Tue, 22 Oct 2019 16:17:16 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Neil Madden <neil.madden@forgerock.com>, Jim Schaad <ietf@augustcellars.com>
CC: "cose@ietf.org" <cose@ietf.org>, "jose@ietf.org" <jose@ietf.org>, ivaylo petrov <ivaylo@ackl.io>
Thread-Topic: =?utf-8?B?W0NPU0VdICBbam9zZV0gIPCflJQgV0dMQyBvZiBkcmFmdC1pZXRmLWNvc2Ut?= =?utf-8?Q?webauthn-algorithms?=
Thread-Index: AQHVbwCfAPK5Y9lIXUekPxghlw4nSac0T3mAgABSv4CAAApZgIAyXDRw
Date: Tue, 22 Oct 2019 16:17:15 +0000
Message-ID: <DM6PR00MB05696F42C452640D3F9C09C4F5680@DM6PR00MB0569.namprd00.prod.outlook.com>
References: <CAJFkdRzEF0wh9-H4dDNQeUHVd_VD8KKv1jOJ7BWs+bKN2e6gBQ@mail.gmail.com> <CAJFkdRy6Bs77gFGG0QGMC1fe_niQC6Of7_2Z8+jjYzpWkuMDBQ@mail.gmail.com> <465EE321-1595-4453-8D4E-E3A6A457C86E@forgerock.com> <012001d56fc0$1fb30e90$5f192bb0$@augustcellars.com> <F6FF776D-FFF9-4330-8A6B-81F783D990C2@forgerock.com>
In-Reply-To: <F6FF776D-FFF9-4330-8A6B-81F783D990C2@forgerock.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=03b5b886-7751-4615-96ea-0000eb766e27; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-10-22T16:11:41Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Jones@microsoft.com;
x-originating-ip: [50.47.93.218]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 55a49ad3-3cb1-442a-f5b4-08d7570b4df3
x-ms-traffictypediagnostic: DM6PR00MB0521:
x-microsoft-antispam-prvs: <DM6PR00MB05211A03E59626D5D5715E75F5680@DM6PR00MB0521.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01986AE76B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(366004)(396003)(39860400002)(346002)(136003)(376002)(199004)(189003)(51914003)(71190400001)(25786009)(256004)(316002)(22452003)(10090500001)(8990500004)(110136005)(2906002)(33656002)(790700001)(6116002)(3846002)(81166006)(7696005)(76176011)(86362001)(81156014)(486006)(54906003)(6506007)(53546011)(71200400001)(7736002)(8936002)(99286004)(4326008)(6436002)(9686003)(476003)(11346002)(446003)(54896002)(102836004)(55016002)(6306002)(186003)(236005)(26005)(76116006)(66946007)(66476007)(6246003)(66556008)(66446008)(74316002)(66066001)(64756008)(10290500003)(52536014)(14454004)(5660300002)(229853002)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR00MB0521; H:DM6PR00MB0569.namprd00.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5qBwVqyLcWFGpOK14aS182nXeQXS9mAueT1T0t6zt8LfAqtevhYDRBGdS+vMR3PlPlFI+egldFYXRsvH6LeB8pN1xd2LU6WHJk87DRcGBX4i5rsPRB9WJqw18rA0o0hBetzY8n7TwOr2tC+MDuSRzsZWA7ntde0EATt1sGP7IJpq4UGT4UAV3CWVtg+h0veYtvgvL6Kgip/S1aKhttVj2EqMoJS4hhbAcQPFXu/lepdD4XNpQ2X5l2eOKhnjjhltCRaAFCrUWjJ/wfEVVRCUrRKBEiHftvkCkzA+0Nw+v9DBZz71SJ1Yn3/pxWrQtGlXE37bJRhKgKcybriBW14u0G38lz8RXlp+o6WvX3frlRsPo1MfHBA4oOJCzfIAN5QhnOQpMKE+qSbDu6idHr3ofMiZAWCu2KOHMhjP3WgmD0TqDYHPWO8JofHXUqkEphjF
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR00MB05696F42C452640D3F9C09C4F5680DM6PR00MB0569namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 55a49ad3-3cb1-442a-f5b4-08d7570b4df3
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2019 16:17:15.9435 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: JqM2xSBqqQSieQmAY/HQ/9wbwjHIK41hacy7iREH/emyXRZFtBPtbfwoZLLIpVpVz17rZtiOZH9Bdt0I/rZYOA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR00MB0521
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/qcPF7DkiBX_OVxBhWnfrRgaY4To>
Subject: Re: [jose] =?utf-8?q?=5BCOSE=5D____=F0=9F=94=94_WGLC_of_draft-ietf-c?= =?utf-8?q?ose-webauthn-algorithms?=
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 22 Oct 2019 16:17:47 -0000

Thanks again for the review, Neil.  My replies are inline, prefixed by “Mike>”.

                                                       -- Mike

From: COSE <cose-bounces@ietf.org> On Behalf Of Neil Madden
Sent: Friday, September 20, 2019 8:09 AM
To: Jim Schaad <ietf@augustcellars.com>
Cc: cose@ietf.org; jose@ietf.org; ivaylo petrov <ivaylo@ackl.io>
Subject: Re: [COSE] [jose] 🔔 WGLC of draft-ietf-cose-webauthn-algorithms

Thanks for the reply, comments in-line marked with [NEM]:


On 20 Sep 2019, at 15:31, Jim Schaad <ietf@augustcellars.com<mailto:ietf@augustcellars.com>> wrote:



From: jose <jose-bounces@ietf.org<mailto:jose-bounces@ietf.org>> On Behalf Of Neil Madden
Sent: Friday, September 20, 2019 2:35 AM
To: ivaylo petrov <ivaylo@ackl.io<mailto:ivaylo@ackl.io>>
Cc: jose@ietf.org<mailto:jose@ietf.org>; cose@ietf.org<mailto:cose@ietf.org>
Subject: Re: [jose] 🔔 WGLC of draft-ietf-cose-webauthn-algorithms

Thanks, I wasn't aware of this draft. It looks ok, just a few comments from me:

secp256k1 is mentioned in the context of signatures and the new ES256K JWS algorithm, but when it is registered in the JOSE Elliptic Curve registry it will also be usable for ECDH-ES encryption. The current draft mentions JOSE but only links to RFC 7515 (JWS). Is the intention that the curve be only used for signatures, or is it also intended for encryption?

[JLS] That is an interesting question.  Right now I would say that it is only for signatures, but it could be expanded to key agreement quite easily.  Is there any need for it or are you just speculating?  The big use I know of is bit coin which is only signatures and WebAuthn which is only signatures.

[NEM] As soon as it is registered as a JOSE elliptic curve it can be used for ECDH-ES, so the draft should make a statement one way or another as to whether this is intended rather than standardizing that usage by side-effect IMO.

Mike> Having thought about this some more, given that no one on the thread has presented an argument why secp256k1 should or should not be used with ECDH-ES, I now plan to make an explicit statement that whether it can or cannot be used is explicitly out of scope of this specification, and the topic could be covered by a future specification.  The question doesn’t have to be decided to achieve the goals of the current specification.

I'm glad RS1 is not being registered for JOSE, although I'm still a bit surprised that it is being registered (even as deprecated) for a standard as new as COSE. I can't find any justification in the linked WebAuthn or CTAP specs for why this algorithm needs to exist at all. Section 5.3 says that it needs to be registered because some WebAuthn TPM attestations use it, but the very same section says that the algorithm MUST NOT be used by COSE implementations (is a WebAuthn implementation not a COSE implementation?). If the normative language in the spec is obeyed then the algorithm will never be used and so the registered identifier isn't needed.

[JLS] For better or for worse, RS1 is already registered for JOSE, so that is the reason it is not registered here.

Ouch, I hadn't seen this. The WebCrypto group really did a number on the registry. Thankfully most of them (including RS1) are only registered for JWK usage and marked as Prohibited. (What does it even mean for things like "A128CBC" to be registered as a JWK "alg" value?)

My main point still stands that section 5.3 of the draft is self-contradictory as it says that the reason for registry is because some TPMs are using the algorithm but then also says that those implementations MUST NOT use the algorithm, negating the reason for registering it in the first place.

Mike> I will include the explanation arrived at in the discussion on the JOSE mailing list.

-- Neil