[lamps] CSR attrs in rfc7030-clarify
Russ Housley <housley@vigilsec.com> Thu, 11 June 2020 15:00 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 AB2E13A091E for <spasm@ietfa.amsl.com>; Thu, 11 Jun 2020 08:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 kUq9tI64Snhm for <spasm@ietfa.amsl.com>; Thu, 11 Jun 2020 08:00:00 -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 1F8C73A091B for <spasm@ietf.org>; Thu, 11 Jun 2020 08:00:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 9A6C9300B6A for <spasm@ietf.org>; Thu, 11 Jun 2020 10:59:57 -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 ELu3Vo1xDexU for <spasm@ietf.org>; Thu, 11 Jun 2020 10:59:56 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-72-66-113-56.washdc.fios.verizon.net [72.66.113.56]) by mail.smeinc.net (Postfix) with ESMTPSA id 3D04D300A01; Thu, 11 Jun 2020 10:59:56 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Message-Id: <DF151F0E-BE45-4FA1-9448-321555814FF0@vigilsec.com>
Date: Thu, 11 Jun 2020 10:59:57 -0400
Cc: LAMPS <spasm@ietf.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Tul0pU4_zsVjWK1U4iMjTfsY9yU>
Subject: [lamps] CSR attrs in rfc7030-clarify
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: Thu, 11 Jun 2020 15:00:02 -0000
Michael:
I have had an email exchange with someone that implemented EST, and they have pointed out that the aa-asymmDecryptKeyID attribute is not for inclusion in the CSR. However, when the server does the public/private key pair generation, it is used to name the key to be used top protect the server-generated key.
This leads to two changes in rfc7030-clarify:
In Section 4.1:
OLD:
AttrSet ATTRIBUTE ::= { aa-asymmDecryptKeyID, ... }
NEW:
AttrSet ATTRIBUTE ::= { ... }
In Appendix A:
OLD:
AttrSet ATTRIBUTE ::= { aa-asymmDecrytKeyID, ... }
NEW:
AttrSet ATTRIBUTE ::= { ... }
Thanks,
Russ
- [lamps] CSR attrs in rfc7030-clarify Russ Housley
- Re: [lamps] CSR attrs in rfc7030-clarify Michael Richardson
- Re: [lamps] CSR attrs in rfc7030-clarify Russ Housley