Re: NIST publishes new DSA draft

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

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLSI5-0000SQ-6h for openpgp-archive@lists.ietf.org; Mon, 20 Mar 2006 16:51:53 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLSI4-0005N0-RS for openpgp-archive@lists.ietf.org; Mon, 20 Mar 2006 16:51:53 -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 k2KLZWlV030022; Mon, 20 Mar 2006 14:35: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 k2KLZWvK030021; Mon, 20 Mar 2006 14:35: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 k2KLZVwU030014 for <ietf-openpgp@imc.org>; Mon, 20 Mar 2006 14:35:32 -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 k2KLZUk08791; Mon, 20 Mar 2006 16:35:30 -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 k2KLZS6c007309; Mon, 20 Mar 2006 16:35:28 -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 k2KLZOis004182; Mon, 20 Mar 2006 16:35:24 -0500
Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id k2KLZNtX004181; Mon, 20 Mar 2006 16:35:23 -0500
Date: Mon, 20 Mar 2006 16:35:23 -0500
From: David Shaw <dshaw@jabberwocky.com>
To: Tony Hansen <tony@att.com>
Cc: OpenPGP <ietf-openpgp@imc.org>
Subject: Re: NIST publishes new DSA draft
Message-ID: <20060320213523.GB3994@jabberwocky.com>
Mail-Followup-To: Tony Hansen <tony@att.com>, OpenPGP <ietf-openpgp@imc.org>
References: <20060314194447.4D59A57FB0@finney.org> <20060316192823.GA9945@jabberwocky.com> <441ACF45.704@systemics.com> <87fylhdq36.fsf@wheatstone.g10code.de> <20060317174937.GC13241@jabberwocky.com> <3C3EAEDD-7724-4E92-AA3C-49B5B2E6F3F9@callas.org> <20060320202841.GA3994@jabberwocky.com> <441F19CC.9080004@att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <441F19CC.9080004@att.com>
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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

No, it is not the same output, but it is the same amount of security.
Which hash and which IV doesn't matter here - just that the end result
is 224 bits long.

David

On Mon, Mar 20, 2006 at 04:08:28PM -0500, Tony Hansen wrote:
> 
> Just a quibble. Truncating sha-256 down to 224 bits does not give the
> same output as sha-224, as sha-256 and sha-224 use different
> initialization vectors. So "truncated sha-256" and "sha-224" really
> would be totally different hash values.
> 
> No comment on the rest of what you say.
> 
> 	Tony Hansen
> 	tony@att.com
> 
> David Shaw wrote:
> > I understand the argument about wanting 128 bits of security, but
> > since the new DSA allows a 224 bit q, there just isn't room for 128
> > bits of security.  Whether we truncate SHA-256 and call it "truncated
> > SHA-256" or truncate SHA-256 and call it "SHA-224", we have to
> > truncate.