IETF Logo Mail Archive

Re: Suggested changes for DSA2

David Shaw <dshaw@jabberwocky.com> Mon, 27 March 2006 22:51 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FO0Yd-0004aP-5t for openpgp-archive@lists.ietf.org; Mon, 27 Mar 2006 17:51:31 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FO0Yb-0000Jr-Qg for openpgp-archive@lists.ietf.org; Mon, 27 Mar 2006 17:51:31 -0500
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k2RMWWSO023191; Mon, 27 Mar 2006 15:32:32 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k2RMWW9m023190; Mon, 27 Mar 2006 15:32:32 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org)
X-Authentication-Warning: balder-227.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 balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k2RMWVcI023184 for <ietf-openpgp@imc.org>; Mon, 27 Mar 2006 15:32:31 -0700 (MST) (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 k2RMWNk19287; Mon, 27 Mar 2006 17:32:23 -0500
Received: from grover.jabberwocky.com ([172.24.84.28]) by walrus.hsd1.ma.comcast.net (8.13.6/8.13.5) with ESMTP id k2RMWQ8q018805; Mon, 27 Mar 2006 17:32:26 -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 k2RMWH7G026234; Mon, 27 Mar 2006 17:32:17 -0500
Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id k2RMWH7V026233; Mon, 27 Mar 2006 17:32:17 -0500
Date: Mon, 27 Mar 2006 17:32:16 -0500
From: David Shaw <dshaw@jabberwocky.com>
To: Hal Finney <hal@finney.org>
Cc: ietf-openpgp@imc.org
Subject: Re: Suggested changes for DSA2
Message-ID: <20060327223216.GA25952@jabberwocky.com>
Mail-Followup-To: Hal Finney <hal@finney.org>, ietf-openpgp@imc.org
References: <20060327220815.2716157FAE@finney.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20060327220815.2716157FAE@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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

On Mon, Mar 27, 2006 at 02:08:15PM -0800, "Hal Finney" wrote:
> 
> As an implementor, the question remains: when I verify a signature, what
> q sizes should I allow for a given p?  For example, what q is OK for a p
> of 1536?  What q is OK for a p of 4096?  Should I just make something up?
> How is that going to promote interoperability?

For implementation of signature verification you can just take p and q
straight from the public key.  You don't need to guess since the key
has all the information you need.

David

v2.23.0 | Report a Bug | By Email