Secret key transport

David Shaw <dshaw@jabberwocky.com> Wed, 14 December 2005 14:15 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmXPz-00087w-Ug for openpgp-archive@megatron.ietf.org; Wed, 14 Dec 2005 09:15:46 -0500
Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29941 for <openpgp-archive@lists.ietf.org>; Wed, 14 Dec 2005 09:14:33 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id jBEDuHdY019155; Wed, 14 Dec 2005 05:56:17 -0800 (PST) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id jBEDuHKH019154; Wed, 14 Dec 2005 05:56:17 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from foobar.cs.jhu.edu (foobar.cs.jhu.edu [128.220.13.173]) by above.proper.com (8.12.11/8.12.9) with ESMTP id jBEDuGGe019143 for <ietf-openpgp@imc.org>; Wed, 14 Dec 2005 05:56:17 -0800 (PST) (envelope-from dshaw@jabberwocky.com)
Received: from walrus.hsd1.ma.comcast.net (walrus.hsd1.ma.comcast.net [24.60.132.70]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id jBEDuFS12203 for <ietf-openpgp@imc.org>; Wed, 14 Dec 2005 08:56:15 -0500
Received: from grover.jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.hsd1.ma.comcast.net (8.12.8/8.12.8) with ESMTP id jBEDuDX6014467 for <ietf-openpgp@imc.org>; Wed, 14 Dec 2005 08:56:13 -0500
Received: from grover.jabberwocky.com (grover.jabberwocky.com [127.0.0.1]) by grover.jabberwocky.com (8.13.1/8.13.1) with ESMTP id jBEDu9ts022957 for <ietf-openpgp@imc.org>; Wed, 14 Dec 2005 08:56:09 -0500
Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id jBEDu9in022956 for ietf-openpgp@imc.org; Wed, 14 Dec 2005 08:56:09 -0500
Date: Wed, 14 Dec 2005 08:56:09 -0500
From: David Shaw <dshaw@jabberwocky.com>
To: ietf-openpgp@imc.org
Subject: Secret key transport
Message-ID: <20051214135609.GA22783@jabberwocky.com>
Mail-Followup-To: ietf-openpgp@imc.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc
User-Agent: Mutt/1.5.11
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>

Well into comically late in the game here, but a question recently
came up about the secret key transport format.  Namely, is there one?
2440bis has a public key transport format (the whole of section 10.1),
and the format of secret key and secret subkey packets is defined, but
there doesn't seem to be an analogue to section 10.1 for secret keys.

For example, I've seen secret keys in this format:

 - Secret key packet
 - User ID packet
 - Selfsig on user ID
 - Secret subkey packet
 - Selfsig on subkey

I've also seen secret keys in this format:

 - Secret key packet
 - User ID packet
 - Secret subkey packet

 (i.e. missing the selfsigs).

The first example strikes me as preferable as there is a mild benefit
to having the secret key format parallel the public key format in that
an implementation can extract the public key from the secret key
automatically.  The second example requires a public key to be sent in
addition to the secret key to get the selfsigs (while the selfsig on
the user ID is optional, the one on the subkey isn't).

Either way, though, 2440bis seems silent on this subject.  Is this
something that needs a line or two of text?

David