Re: Mandatory Algorithm Changes?

Ian G <iang@systemics.com> Wed, 09 February 2005 12:43 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 HAA25177 for <openpgp-archive@lists.ietf.org>; Wed, 9 Feb 2005 07:43:19 -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 j19CKcfW013323; Wed, 9 Feb 2005 04:20:38 -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 j19CKcKn013322; Wed, 9 Feb 2005 04:20:38 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from www.enhyper.com (mailgate.enhyper.com [62.49.250.18]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j19CKWG4013248 for <ietf-openpgp@imc.org>; Wed, 9 Feb 2005 04:20:37 -0800 (PST) (envelope-from iang@systemics.com)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by www.enhyper.com (8.11.6/8.11.6) with SMTP id j19DKHr14672 for <ietf-openpgp@imc.org>; Wed, 9 Feb 2005 13:20:22 GMT
X-Authentication-Warning: www.enhyper.com: localhost.localdomain [127.0.0.1] didn't use HELO protocol
Message-ID: <420A012A.5020204@systemics.com>
Date: Wed, 09 Feb 2005 12:25:14 +0000
From: Ian G <iang@systemics.com>
Organization: http://financialcryptography.com/
User-Agent: Mozilla Thunderbird 1.0 (X11/20050108)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-openpgp@imc.org
Subject: Re: Mandatory Algorithm Changes?
References: <20050208194442.F2C6A57E2A@finney.org> <42092EC2.9040501@systemics.com> <87zmyeyyg9.fsf@wheatstone.g10code.de>
In-Reply-To: <87zmyeyyg9.fsf@wheatstone.g10code.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
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>
Content-Transfer-Encoding: 7bit

Werner Koch wrote:

>On Tue, 08 Feb 2005 21:27:30 +0000, Ian G said:
>
>  
>
>>If both of the major OpenPGP implementations
>>already support it, is there any reason to doubt
>>the little guys will follow along eventually?
>>    
>>
>
>There are other implementations using OpenPGP as well.  For embedded
>systems adding another MUST cipher is a problem, in particular if 3DES
>is already done in (old) hardware.  There might also be the need to
>implement the preferences system unless both, 3DES and AES, are
>declared as fallback algorithms.
>  
>

Right, in that it's a given that there are always
problems for any change.  But let's explore this
a bit more.

What is being changed (suggested) is the OpenPGP
RFC - standard.  No implementation needs to change,
and the only implementations that would want to
change would be future ones that need to adhere
to the standard.

Embedded devices don't really need to adhere
(here, I am assuming that such embedded are
totally embedded and aren't communicating
with the open email community).

Also, as time goes on, those that do not support
AES are going to raise more and more eyebrows.
I think the time is going to come fairly shortly
where I'd say "implementing AES" was more
important than "slavishly following the standard
in every detail."

Are there any little guys here would like to add
anything?  Positive or negative?

FTR: Edwin informs me that the Cryptix OpenPGP
has no objection.

(Which should be taken to mean I vote for the
change - I'm just playing the devil's advocate here.)

iang

-- 
News and views on what matters in finance+crypto:
        http://financialcryptography.com/