IETF Logo Mail Archive

Re: [openpgp] [PATCH] RFC4880bis: Argon2i

ianG <iang@iang.org> Tue, 03 November 2015 03:52 UTC

Return-Path: <iang@iang.org>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A021B2C70 for <openpgp@ietfa.amsl.com>; Mon, 2 Nov 2015 19:52:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vN_SrxQNo33A for <openpgp@ietfa.amsl.com>; Mon, 2 Nov 2015 19:52:19 -0800 (PST)
Received: from virulha.pair.com (virulha.pair.com [209.68.5.166]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98F891ACE1F for <openpgp@ietf.org>; Mon, 2 Nov 2015 19:52:19 -0800 (PST)
Received: from tormenta.local (iang.org [209.197.106.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by virulha.pair.com (Postfix) with ESMTPSA id C15286D724; Mon, 2 Nov 2015 22:52:17 -0500 (EST)
To: openpgp@ietf.org
References: <5623AA95.4060903@googlemail.com> <874mh3q3ol.fsf@alice.fifthhorseman.net>
From: ianG <iang@iang.org>
Message-ID: <56382F70.5000501@iang.org>
Date: Tue, 03 Nov 2015 03:52:16 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <874mh3q3ol.fsf@alice.fifthhorseman.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/ZfH37s5U4AF0sWVFIYBBgTd2GeE>
Subject: Re: [openpgp] [PATCH] RFC4880bis: Argon2i
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2015 03:52:20 -0000

On 3/11/2015 01:20 am, Daniel Kahn Gillmor wrote:
> If we introduce this as a normative dependency for OpenPGP,


I agree with all the rest, but can we also deprecate some old stuff as well?

Can we construct a plan e.g., that no existing S2K be used with new keys 
and the new form not be used with old keys?

Or *something* to avoid the monotonically increasing algorithmic bloat 
that seems so trendy.



iang

v2.23.0 | Report a Bug | By Email