Re: [Cose] Issue: Create separate MAC structure

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 22 April 2015 06:57 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 936F31B323D for <cose@ietfa.amsl.com>; Tue, 21 Apr 2015 23:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 qMcJEMXFHOoO for <cose@ietfa.amsl.com>; Tue, 21 Apr 2015 23:57:39 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 093141B3235 for <cose@ietf.org>; Tue, 21 Apr 2015 23:57:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C7E26BED6; Wed, 22 Apr 2015 07:57:37 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6StUXPMFo2M1; Wed, 22 Apr 2015 07:57:36 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.17.62]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5A578BE32; Wed, 22 Apr 2015 07:57:36 +0100 (IST)
Message-ID: <55374660.4030606@cs.tcd.ie>
Date: Wed, 22 Apr 2015 07:57:36 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Jim Schaad <ietf@augustcellars.com>, cose@ietf.org
References: <018701d07cb1$77705310$6650f930$@augustcellars.com>
In-Reply-To: <018701d07cb1$77705310$6650f930$@augustcellars.com>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/cose/FAtHuXNl-VEmE41NSPNBmb8ORWI>
Subject: Re: [Cose] Issue: Create separate MAC structure
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Apr 2015 06:57:40 -0000


On 22/04/15 05:04, Jim Schaad wrote:
> Question:  Should we separate out MACs from Signatures?
> 
> Discussion:
> 
> I have a number of reasons that I would support this change:
> 
> .  It is easier to talk about the security properties of signatures and MACs
> if they are not combined into a single structure.  The security properties
> of the two items are very different and conflating them does not make for
> good decisions by people who are using the message format.
> 
> * It is problematic to do recipient key management if they are in the same
> structure.  The fact that signers and recipients have different structures,
> means that overlapping them can lead to implementation errors if a recipient
> structure is used when a signer structure is called for.  One way that has
> been conceived to do the recipient management can be found in
> http://datatracker.ietf.org/doc/draft-jones-jose-key-managed-json-web-signat
> ure. 
> 
> *  Having MAC different from Signatures allows for the ability to do a clean
> separation of MAC and signature code implementations when only one of them
> is needed.
> 
> Why it should not be done:
> 
> *  There might be confusion of people moving from JOSE to COSE.

You gotta choose who to confuse:-)

I agree with you - I'd prefer separating MACs and signatures at
as high a level as possible. Consuming code needs to know the
difference and should have a smaller footprint if these concepts
are not conflated and if only one of MACs or signature needs to
be supported by a device/application.

S.

> 
> Jim
> 
> 
> _______________________________________________
> Cose mailing list
> Cose@ietf.org
> https://www.ietf.org/mailman/listinfo/cose
>