Re: [openpgp] Proposal to include AEAD OCB mode to 4880bis

Paul Wouters <paul@nohats.ca> Mon, 30 October 2017 18:01 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3B1D98B5 for <openpgp@ietfa.amsl.com>; Mon, 30 Oct 2017 11:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_QP_LONG_LINE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 biynXKuSSVBJ for <openpgp@ietfa.amsl.com>; Mon, 30 Oct 2017 11:00:57 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC21798AD for <openpgp@ietf.org>; Mon, 30 Oct 2017 11:00:57 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3yQj2b3KMQzF76; Mon, 30 Oct 2017 19:00:55 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1509386455; bh=26SxNosYMKCagpLbxldwqolr3oZHgvArmFb8O9cIg9c=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=AkKd6yb0qXftmPwoio7edTGm3h3K4sxhfQ9c0BmuhE1MXCZ4q3d7FAvS1y0/mEn1O /Z8wKqaul3WvtCsSARtBp2RtO62zVlXwpfkE9Z314RzQ48PDWCOwgUFw36LOAaw+80 bJ4nIDyx6PnCrufnoqon4NDcIkMvCKaYTScnHKF8=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 5ezaqyrT7Fmn; Mon, 30 Oct 2017 19:00:53 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 30 Oct 2017 19:00:53 +0100 (CET)
Received: from [10.252.1.42] (unknown [2.50.18.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 0709F62D29; Mon, 30 Oct 2017 14:00:52 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 0709F62D29
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (15A432)
In-Reply-To: <59F74542.5080409@openfortress.nl>
Date: Mon, 30 Oct 2017 22:00:47 +0400
Cc: Derek Atkins <derek@ihtfp.com>, "openpgp@ietf.org" <openpgp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <37D92E03-5071-42AC-B057-AA3C18B0762A@nohats.ca>
References: <D0505748-E376-4CF9-8906-9AD77838FB23@ribose.com> <alpine.LRH.2.21.1710251219190.18006@bofh.nohats.ca> <59F0C015.2050303@openfortress.nl> <sjmbmko1x4i.fsf@securerf.ihtfp.org> <59F74542.5080409@openfortress.nl>
To: Rick van Rein <rick@openfortress.nl>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/AZMbaGkCl1L-b657Z-yOrekTEv4>
Subject: Re: [openpgp] Proposal to include AEAD OCB mode to 4880bis
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 30 Oct 2017 18:01:10 -0000

On Oct 30, 2017, at 19:29, Rick van Rein <rick@openfortress.nl> wrote:
> 
> Hi Derek,
> 
>> 
>> I have files encrypted 20+ years ago (to a 20+ year old key) sitting
>> around in storage.  Are you saying that those encrypted files should not
>> be readable anymore?

So when do we stop supporting an algorithm? When it can be brute forces in a month? A year ? A day?


> One might question if current-day crypto software should continue to
> support old encrypted files though, or that a fork would be wiser.

Like pgp 2.6 and pgp 5. Yes.

A way to also stimulate upgrading could be to demote algorithms to decrypt/verify only and not allow them for creating new encrypted/signed material.

As for we have been doing this for  20 years argument, I am still carrying idea.c and still have to manually compile it every time gpg upgrades. So the “current” scheme has proven to not work well at all for me.

Paul