IETF Logo Mail Archive

Mandatory Algorithm Changes?

Jon Callas <jon@callas.org> Tue, 08 February 2005 18:16 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 NAA01305 for <openpgp-archive@lists.ietf.org>; Tue, 8 Feb 2005 13:16:51 -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 j18HhQpR024190; Tue, 8 Feb 2005 09:43:26 -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 j18HhQ1K024189; Tue, 8 Feb 2005 09:43:26 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from merrymeet.com (merrymeet.com [63.73.97.162]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j18HhP8U024180 for <ietf-openpgp@imc.org>; Tue, 8 Feb 2005 09:43:25 -0800 (PST) (envelope-from jon@callas.org)
Received: from keys.merrymeet.com (63.73.97.166) by merrymeet.com with ESMTP (Eudora Internet Mail Server X 3.2.6) for <ietf-openpgp@imc.org>; Tue, 8 Feb 2005 09:43:17 -0800
Received: from [63.73.97.189] ([63.73.97.189]) by keys.merrymeet.com (PGP Universal service); Tue, 08 Feb 2005 09:43:17 -0800
X-PGP-Universal: processed
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Transfer-Encoding: 7bit
Message-Id: <0e2405990b7f7b186cd70e8603889d04@callas.org>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
To: OpenPGP <ietf-openpgp@imc.org>
From: Jon Callas <jon@callas.org>
Subject: Mandatory Algorithm Changes?
Date: Tue, 08 Feb 2005 09:42:20 -0800
X-Mailer: Apple Mail (2.619.2)
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

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?

	Jon

v2.23.0 | Report a Bug | By Email