IETF Logo Mail Archive

Re: How to Calculate Signatures?

David Shaw <dshaw@jabberwocky.com> Mon, 04 April 2005 19:44 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16861 for <openpgp-archive@lists.ietf.org>; Mon, 4 Apr 2005 15:44:42 -0400 (EDT)
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 j34JOs2X060003; Mon, 4 Apr 2005 12:24:54 -0700 (PDT) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j34JOsJJ060002; Mon, 4 Apr 2005 12:24:54 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [216.148.227.89]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j34JOrEI059972 for <ietf-openpgp@imc.org>; Mon, 4 Apr 2005 12:24:54 -0700 (PDT) (envelope-from dshaw@jabberwocky.com)
Received: from walrus.ne.client2.attbi.com ([24.60.132.70]) by comcast.net (rwcrmhc14) with ESMTP id <2005040419244901400ahcjse>; Mon, 4 Apr 2005 19:24:49 +0000
Received: from grover.jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.ne.client2.attbi.com (8.12.8/8.12.8) with ESMTP id j34JOlQr006906 for <ietf-openpgp@imc.org>; Mon, 4 Apr 2005 15:24:47 -0400
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 j34JOjSh022550 for <ietf-openpgp@imc.org>; Mon, 4 Apr 2005 15:24:45 -0400
Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id j34JOj9T022549 for ietf-openpgp@imc.org; Mon, 4 Apr 2005 15:24:45 -0400
Date: Mon, 04 Apr 2005 15:24:45 -0400
From: David Shaw <dshaw@jabberwocky.com>
To: ietf-openpgp@imc.org
Subject: Re: How to Calculate Signatures?
Message-ID: <20050404192445.GD22111@jabberwocky.com>
Mail-Followup-To: ietf-openpgp@imc.org
References: <20050404180805.A9E9F57EBA@finney.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20050404180805.A9E9F57EBA@finney.org>
OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc
User-Agent: Mutt/1.5.8i
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 Mon, Apr 04, 2005 at 11:08:05AM -0700, "Hal Finney" wrote:

> I agree that if it takes that long for the change to propagate, we
> are probably better off waiting for NIST to come up with FIPS 186-3
> which will specify how to use SHA-2 with DSS.

I think it would take a good long while for the change to propagate.

I don't know about other implementations, but there is no support for
this in GnuPG.  Adding support is trivial, to be sure, but getting
however many GnuPG installations to upgrade (with no compatibility
with many DSA signatures in the meantime) would be a pretty
substantial problem.

David

v2.23.0 | Report a Bug | By Email