IETF Logo Mail Archive

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

Rick van Rein <rick@openfortress.nl> Mon, 30 October 2017 15:36 UTC

Return-Path: <rick@openfortress.nl>
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 3D9E613FA93 for <openpgp@ietfa.amsl.com>; Mon, 30 Oct 2017 08:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.221
X-Spam-Level:
X-Spam-Status: No, score=-1.221 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 w3S294LMYISg for <openpgp@ietfa.amsl.com>; Mon, 30 Oct 2017 08:36:13 -0700 (PDT)
Received: from lb2-smtp-cloud7.xs4all.net (lb2-smtp-cloud7.xs4all.net [194.109.24.28]) (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 12F8A1394E4 for <openpgp@ietf.org>; Mon, 30 Oct 2017 08:29:20 -0700 (PDT)
Received: from fame.vanrein.org ([IPv6:2001:980:93a5:1::7]) by smtp-cloud7.xs4all.net with ESMTP id 9C04eMfw6VNbY9C05euuYw; Mon, 30 Oct 2017 16:29:18 +0100
Received: by fame.vanrein.org (Postfix, from userid 1006) id 2A62125DAC; Mon, 30 Oct 2017 15:29:16 +0000 (UTC)
X-Original-To: openpgp@ietf.org
Received: from airhead.local (phantom.vanrein.org [83.161.146.46]) by fame.vanrein.org (Postfix) with ESMTPA id 0F51B25DA9; Mon, 30 Oct 2017 15:29:13 +0000 (UTC)
Message-ID: <59F74542.5080409@openfortress.nl>
Date: Mon, 30 Oct 2017 16:29:06 +0100
From: Rick van Rein <rick@openfortress.nl>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Derek Atkins <derek@ihtfp.com>
CC: "openpgp@ietf.org" <openpgp@ietf.org>
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>
In-Reply-To: <sjmbmko1x4i.fsf@securerf.ihtfp.org>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bogosity: Unsure, tests=bogofilter, spamicity=0.520000, version=1.2.4
X-CMAE-Envelope: MS4wfFxD0z3LgvpsOCpte2ae2Io61apYjNcYvaYwAH5FUdfG35jWibNSOvZfsarXfYbwbIyiw75IbA3JkZ/lOB4uElqlmUPuAUNYshqlxksqrzL/ab2ZLJph KOSUknhMqOXsFxM+4fViUD+dCAvxSL0f4qZWxaTOhbnAZ/PNyniQ4TCzAvpq1s0QfaoEKTcA1xpEfGQsbVa137fEQ01kccecC2w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/QxqQPqs9XdeCk09yyGd0TK0qtQc>
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 15:36:15 -0000

Hi Derek,

>> Along the same lines I'm also surprised that no effort has been made to
>> deprecate 2.x PGP packet formats and public key formats, for instance.
>> We all know that such old keys don't have a reason to exist anymore,
>> but we're all still coding the old and new in order to be compliant to
>> the standards.  Such a waste of time...
>
> 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?

I was thinking about signing, which was indeed an oversight.

One might question if current-day crypto software should continue to
support old encrypted files though, or that a fork would be wiser.  The
added complexity of the software is far from helpful in keeping software
clear and bug free.  Also, this old material may end up being treated by
hardly-tested code, which is another undesirable part.

Anyhow, I brought this up to agree that we should be careful what is
being added, and your response is in fact confirming that.

-Rick

v2.23.0 | Report a Bug | By Email