IETF Logo Mail Archive

Re: NIST publishes new DSA draft

Tony Hansen <tony@att.com> Mon, 20 March 2006 21:30 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRx5-00049S-Sr for openpgp-archive@lists.ietf.org; Mon, 20 Mar 2006 16:30:11 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRx2-0004gA-6c for openpgp-archive@lists.ietf.org; Mon, 20 Mar 2006 16:30:11 -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 k2KL8feR028977; Mon, 20 Mar 2006 14:08:41 -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 k2KL8f4T028975; Mon, 20 Mar 2006 14:08:41 -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 mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id k2KL8eYI028933 for <ietf-openpgp@imc.org>; Mon, 20 Mar 2006 14:08:40 -0700 (MST) (envelope-from tony@att.com)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-7.tower-120.messagelabs.com!1142888912!10043411!1
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 24426 invoked from network); 20 Mar 2006 21:08:32 -0000
Received: from unknown (HELO maillennium.att.com) (134.24.146.4) by server-7.tower-120.messagelabs.com with SMTP; 20 Mar 2006 21:08:32 -0000
Received: from [135.70.80.181] (unknown[135.70.80.181](misconfigured sender)) by maillennium.att.com (mailgw1) with ESMTP id <20060320210832gw100100dee> (Authid: tony); Mon, 20 Mar 2006 21:08:32 +0000
Message-ID: <441F19CC.9080004@att.com>
Date: Mon, 20 Mar 2006 16:08:28 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: OpenPGP <ietf-openpgp@imc.org>
Subject: Re: NIST publishes new DSA draft
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>
In-Reply-To: <20060320202841.GA3994@jabberwocky.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: 856eb5f76e7a34990d1d457d8e8e5b7f

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.

v2.26.15 | Report a Bug | By Email | System Status