Re: V3 secret keys

hal@finney.org ("Hal Finney") Thu, 16 February 2006 18:42 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9o54-000445-SS for openpgp-archive@megatron.ietf.org; Thu, 16 Feb 2006 13:42:18 -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 NAA20612 for <openpgp-archive@lists.ietf.org>; Thu, 16 Feb 2006 13:40:31 -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 k1GIRsAE082501; Thu, 16 Feb 2006 10:27:54 -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 k1GIRsNC082500; Thu, 16 Feb 2006 10:27:54 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from finney.org (226-132.adsl2.netlojix.net [207.71.226.132]) by above.proper.com (8.12.11/8.12.9) with ESMTP id k1GIRrt7082494 for <ietf-openpgp@imc.org>; Thu, 16 Feb 2006 10:27:53 -0800 (PST) (envelope-from hal@finney.org)
Received: by finney.org (Postfix, from userid 500) id 6063B57FAE; Thu, 16 Feb 2006 10:32:11 -0800 (PST)
To: ietf-openpgp@imc.org
Subject: Re: V3 secret keys
Message-Id: <20060216183211.6063B57FAE@finney.org>
Date: Thu, 16 Feb 2006 10:32:11 -0800
From: hal@finney.org
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>

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.

Hal