IETF Logo Mail Archive

Re: [lamps] RFC 5480 clarification for KeyUsages: keyEncipherment and dataEncipherment

Russ Housley <housley@vigilsec.com> Sun, 24 March 2019 06:34 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 023641277D2 for <spasm@ietfa.amsl.com>; Sat, 23 Mar 2019 23:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham 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 1GxTrAJdWy3R for <spasm@ietfa.amsl.com>; Sat, 23 Mar 2019 23:34:12 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 101CB1275F3 for <spasm@ietf.org>; Sat, 23 Mar 2019 23:34:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id BC6F9300ABF for <spasm@ietf.org>; Sun, 24 Mar 2019 02:15:50 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id EIzfxajLQWBF for <spasm@ietf.org>; Sun, 24 Mar 2019 02:15:16 -0400 (EDT)
Received: from dhcp-9347.meeting.ietf.org (dhcp-9347.meeting.ietf.org [31.133.147.71]) by mail.smeinc.net (Postfix) with ESMTPSA id E337F300250; Sun, 24 Mar 2019 02:15:03 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <74609304-E99C-419F-AE9A-00CFDD825927@sn3rd.com>
Date: Sun, 24 Mar 2019 02:33:13 -0400
Cc: "spasm@ietf.org" <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <61B1FE9F-4647-4AE5-BBB0-703B276E51A0@vigilsec.com>
References: <74609304-E99C-419F-AE9A-00CFDD825927@sn3rd.com>
To: Sean Turner <sean@sn3rd.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/CyISBl5NiAYSWPd9RrH_pLOOgjE>
Subject: Re: [lamps] RFC 5480 clarification for KeyUsages: keyEncipherment and dataEncipherment
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Mar 2019 06:34:14 -0000

Sean:
> 
> RFC 5480 enumerates the KeyUsage values that are included for an EC key:
> https://tools.ietf.org/html/rfc5480#section-3
> But, we neglected to mention keyEncipherment and dataEncipherment.  Does that mean these values MAY be included, MUST NOT be included, or something else?  And, is this worth spinning a short draft to clarify RFC 5480?

My understanding is that the algorithms in RFC 5480 are key agreement and digital signature algorithms, so neither keyEncipherment and dataEncipherment are appropriate.  I read it as these bits MUST NOT be set.

Russ

v2.23.0 | Report a Bug | By Email