IETF Logo Mail Archive

Re: [saag] PKIX and related RFCs - definition of Key Packages

Russ Housley <housley@vigilsec.com> Thu, 17 June 2021 13:51 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CF6E3A2072 for <saag@ietfa.amsl.com>; Thu, 17 Jun 2021 06:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable 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 2cMK3K4viB9X for <saag@ietfa.amsl.com>; Thu, 17 Jun 2021 06:50:54 -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 AAFAA3A2073 for <saag@ietf.org>; Thu, 17 Jun 2021 06:50:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id E15FD300BB1 for <saag@ietf.org>; Thu, 17 Jun 2021 09:50:53 -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 Qrp2qj2p5CEv for <saag@ietf.org>; Thu, 17 Jun 2021 09:50:48 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 7B736300231; Thu, 17 Jun 2021 09:50:46 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <F1A6EE33-5CEE-4DA2-88D3-A87133F897CF@ll.mit.edu>
Date: Thu, 17 Jun 2021 09:50:45 -0400
Cc: Peter Gutmann <pgut001@cs.auckland.ac.nz>, IETF SAAG <saag@ietf.org>, "spasm@ietf.org" <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CF9941B-2B02-467B-BC07-B6DD6E5FC6D0@vigilsec.com>
References: <B8006164-51AD-4B3B-9CE7-83B0574294F8@ll.mit.edu> <SY4PR01MB62511B1911DD23ADF0169307EE0E9@SY4PR01MB6251.ausprd01.prod.outlook.com> <F1A6EE33-5CEE-4DA2-88D3-A87133F897CF@ll.mit.edu>
To: Uri Blumenthal <uri@ll.mit.edu>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/4CVXA44uhQOTeCAu_Iy8YHQNcjw>
Subject: Re: [saag] PKIX and related RFCs - definition of Key Packages
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2021 13:51:01 -0000

Uri:

>> I think the short answer is that public keys are usually exchanged by sending certificates.
> 
> I'm not sure I understand - private keys usually are not exchanged at all, and yet there's a whole bunch of ASN.1 stuff describing them.

Yes, this is needed.  For example, PKCS#12 can be used to move a private key from one device to another.

Russ

v2.23.0 | Report a Bug | By Email