Re: Mandatory Algorithm Changes?

Edwin Woudt <edwin@woudt.nl> Tue, 08 February 2005 21:39 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 QAA28566 for <openpgp-archive@lists.ietf.org>; Tue, 8 Feb 2005 16:39:54 -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 j18KNaSG035177; Tue, 8 Feb 2005 12:23:36 -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 j18KNaVu035172; Tue, 8 Feb 2005 12:23:36 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from smtpq2.home.nl (smtpq2.home.nl [213.51.128.197]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j18KNZhq035077 for <ietf-openpgp@imc.org>; Tue, 8 Feb 2005 12:23:36 -0800 (PST) (envelope-from edwin@woudt.nl)
Received: from [213.51.128.136] (port=33198 helo=smtp5.home.nl) by smtpq2.home.nl with esmtp (Exim 4.30) id 1CybtM-0004gc-GI; Tue, 08 Feb 2005 21:23:24 +0100
Received: from cc718542-a.ensch1.ov.home.nl ([84.31.118.254]:5198 helo=[10.24.64.4]) by smtp5.home.nl with esmtp (Exim 4.30) id 1CybtK-000564-Co; Tue, 08 Feb 2005 21:23:22 +0100
Date: Tue, 08 Feb 2005 21:23:22 +0100
From: Edwin Woudt <edwin@woudt.nl>
To: Jon Callas <jon@callas.org>, OpenPGP <ietf-openpgp@imc.org>
Subject: Re: Mandatory Algorithm Changes?
Message-ID: <95D9A97EDD6A76D9F6789F52@[10.24.64.4]>
In-Reply-To: <0e2405990b7f7b186cd70e8603889d04@callas.org>
References: <0e2405990b7f7b186cd70e8603889d04@callas.org>
X-Mailer: Mulberry/4.0.0a4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-AtHome-MailScanner-Information: Neem contact op met support@home.nl voor meer informatie
X-AtHome-MailScanner: Found to be clean
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>
Content-Transfer-Encoding: 7bit

--On 8-2-2005 9:42 -0800 Jon Callas <jon@callas.org> wrote:
>
> I almost cringe to suggest this, but I will.
>
> Triple-DES is pretty much obsolete. Yesterday, I saw that NIST announced
> they're moving to stronger hashes.
>
> Does anyone object to changing the MUST cipher to AES (I'd pick 128) and
> MUST hash to SHA-256?

Regarding SHA-256: would that mean switching to SHA-256 for key 
fingerprints as well? (shouldn't v5 keys be introduced then?) And use 
SHA-256 for MDC packets?

Or is it just adding a MUST implement, so applications can use SHA-256 for 
document signatures with RSA keys only? (as DSA forces one to use SHA-1 
anyway)

IMHO, the first is what should be done at some point, but that's a really 
big change: all implementations out there need to be upgraded. Wouldn't 
that conflict with getting the current draft on standards track?

I do not see the point of the second option: as long as keys are only 
protected by a 160 bit figerprint, there is not much point protecting 
document signatures with longer hashes. It may be harder to generate a 
collision resulting in a valid key, then it is to generate a collision 
resulting in just some other random document, but I do not think it is wise 
to count on such an assumption.

-- 
Edwin