Re: V3 secret keys

David Shaw <dshaw@jabberwocky.com> Thu, 16 February 2006 19:03 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9oPA-0001Bc-EX for openpgp-archive@megatron.ietf.org; Thu, 16 Feb 2006 14:03:04 -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 OAA22678 for <openpgp-archive@lists.ietf.org>; Thu, 16 Feb 2006 14:01: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 k1GIml94083717; Thu, 16 Feb 2006 10:48:47 -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 k1GImlnM083716; Thu, 16 Feb 2006 10:48:47 -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 k1GImkGs083710 for <ietf-openpgp@imc.org>; Thu, 16 Feb 2006 10:48:46 -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 k1GImik03847 for <ietf-openpgp@imc.org>; Thu, 16 Feb 2006 13:48:44 -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 k1GImjX6014567 for <ietf-openpgp@imc.org>; Thu, 16 Feb 2006 13:48:45 -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 k1GImdEV017967 for <ietf-openpgp@imc.org>; Thu, 16 Feb 2006 13:48:39 -0500
Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id k1GImcgm017966 for ietf-openpgp@imc.org; Thu, 16 Feb 2006 13:48:38 -0500
Date: Thu, 16 Feb 2006 13:48:38 -0500
From: David Shaw <dshaw@jabberwocky.com>
To: ietf-openpgp@imc.org
Subject: Re: V3 secret keys
Message-ID: <20060216184838.GC17725@jabberwocky.com>
Mail-Followup-To: ietf-openpgp@imc.org
References: <20060216183211.6063B57FAE@finney.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20060216183211.6063B57FAE@finney.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 Thu, Feb 16, 2006 at 10:32:11AM -0800, "Hal Finney" wrote:
> 
> Peter Gutmann writes:
> >> Why not just include the pseudocode (or more usefully straight C code) for
> >> the operation? That's the ultimate definitive description, any programmer
> >> can understand it, and you don't run into the problems you do with the
> >> english description.
> >>
> >> (Even if an implementer doesn't understand it, they can always just cut &
> >> paste the code).
> 
> We do have an extremely verbose, algorithmic description of the encrypted
> message CFB mode, in section 12.8.  It's basically English language
> pseudocode.  We could add another section for the somewhat-similar V3
> key decryption, I guess.  Seems like a lot of work for functionality
> that we would hope to be deprecating, but I know people do need it to
> work with the large body of V3 keys.

If the language in 1991 is suitable, perhaps we could just point to
1991.  Is it legal to refer in this way to a document that we're
obsoleting in 2440bis?

David