[core] draft-ietf-core-oscore-groupcomm: Question signature length

Jim Schaad <ietf@augustcellars.com> Thu, 10 January 2019 03:44 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A75F1131118; Wed, 9 Jan 2019 19:44:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.794
X-Spam-Level:
X-Spam-Status: No, score=-0.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 q0DD0aMipCS1; Wed, 9 Jan 2019 19:44:46 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 079F3131113; Wed, 9 Jan 2019 19:44:46 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 9 Jan 2019 19:44:18 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: draft-ietf-core-oscore-groupcomm@ietf.org
CC: core@ietf.org
Date: Wed, 09 Jan 2019 19:44:13 -0800
Message-ID: <000601d4a896$c298edb0$47cac910$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdSolcHgZsXD4+t9SiaVRYjDg8drww==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/AKvGeWID_6l4dXIl3tZy5iHYzRs>
Subject: [core] draft-ietf-core-oscore-groupcomm: Question signature length
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2019 03:44:48 -0000

I want to verify that you understand the following is true.

It is not possible based on just the content of the message to determine
where the encrypted body ends and the signature begins.  

To see why this is the case, if the signature algorithm in the context is
EdDSA then it could be either signed with the x25519 curve or the x448
curve.  The same thing is true with ECDSA signatures as the value ES256
implies that the hash used is SHA-256 but it does not require that the curve
used to sign is P-256.  It can be any of the curves that would be valid for
this hash function.

It might be nicer if there was a signature length encoded someplace so that
the two values can easily be separated.

Jim