Re: Some -15 text nits

David Shaw <dshaw@jabberwocky.com> Thu, 29 December 2005 00:41 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ErlrF-0002lH-QM for openpgp-archive@megatron.ietf.org; Wed, 28 Dec 2005 19:41:29 -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 TAA11757 for <openpgp-archive@lists.ietf.org>; Wed, 28 Dec 2005 19:40:16 -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 jBT0P3gP068356; Wed, 28 Dec 2005 16:25:03 -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 jBT0P3dp068355; Wed, 28 Dec 2005 16:25:03 -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 jBT0P264068347 for <ietf-openpgp@imc.org>; Wed, 28 Dec 2005 16:25:03 -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 jBT0P0S03060 for <ietf-openpgp@imc.org>; Wed, 28 Dec 2005 19:25:00 -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 jBT0P0X6012581 for <ietf-openpgp@imc.org>; Wed, 28 Dec 2005 19:25:00 -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 jBT0Os53005788 for <ietf-openpgp@imc.org>; Wed, 28 Dec 2005 19:24:54 -0500
Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id jBT0Osf1005787 for ietf-openpgp@imc.org; Wed, 28 Dec 2005 19:24:54 -0500
Date: Wed, 28 Dec 2005 19:24:54 -0500
From: David Shaw <dshaw@jabberwocky.com>
To: ietf-openpgp@imc.org
Subject: Re: Some -15 text nits
Message-ID: <20051229002454.GA5579@jabberwocky.com>
Mail-Followup-To: ietf-openpgp@imc.org
References: <20051130161356.GB23127@jabberwocky.com> <FB654B52-503B-4871-AE63-780A52CBBBF6@callas.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <FB654B52-503B-4871-AE63-780A52CBBBF6@callas.org>
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>

On Wed, Dec 28, 2005 at 02:17:45PM -0800, Jon Callas wrote:

> >In section 5.2.1. Signature Types, the signature class 0x18
> >description says "This signature is calculated directly on the subkey
> >itself, not on any User ID or other packets", but in fact 0x18
> >signatures are calculated on the primary key plus subkey.  Similarly,
> >the 0x19 description says "This signature is calculated directly on
> >the primary key itself, and not on any User ID or other packets", but
> >in reality it is calculated exactly the same way as 0x18 is
> >(primary+subkey).
> >
> >To be sure, 5.2.4 gets this right, and 5.2.1 defers to 5.2.4, but it
> >would still be nice to not give two different answers for this.
> >
> 
> fixed. Here's what they say now:
> 
>    0x18: Subkey Binding Signature
>        This signature is a statement by the top-level signing key that
>        indicates that it owns the subkey. This signature is calculated
>        directly on the primary key and subkey, not on any User ID or
>        other packets. A signature that binds a signing subkey MUST have
>        an embedded signature subpacket in this binding signature which
>        contains a 0x19 signature made by the signing subkey on the
>        primary key.
> 
>    0x19 Primary Key Binding Signature
>        This signature is a statement by a signing subkey, indicating
>        that it is owned by the primary key and subkey. This signature
>        is calculated directly on the primary key itself, and not on any
>        User ID or other packets.

Minor problem here: 0x19 hashes both the primary key and subkey.  It
is actually the same as 0x18.

David