Re: [openpgp] [FORGED] Re: Expiration impending: <draft-ietf-openpgp-rfc4880bis-01.txt>

Peter Gutmann <pgut001@cs.auckland.ac.nz> Tue, 04 July 2017 09:06 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
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 2A360131C36 for <openpgp@ietfa.amsl.com>; Tue, 4 Jul 2017 02:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=auckland.ac.nz
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 TNOknnh7GMDs for <openpgp@ietfa.amsl.com>; Tue, 4 Jul 2017 02:06:13 -0700 (PDT)
Received: from mx4.auckland.ac.nz (mx4.auckland.ac.nz [130.216.125.248]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B170E131C33 for <openpgp@ietf.org>; Tue, 4 Jul 2017 02:06:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1499159172; x=1530695172; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=XG3aOOvb1yPskRVbZsMF/OnMjFDcipZlQWEmak5ifOk=; b=aJVnu3alrKFAAljHNb2MRwWQl/47NfO4OzNfE9z+1naGsqm9+GgIydVY tWEtDDGewEsx4O8kane9r6j91BwdOyRnn9K6VOKp0/S33EU99orHrnafG 8RJEmS1fwlWogQ8Wt9U/88uwpHeZ6lQKmukeuBCAWohm20fXFvRkrBnLf UwmvkuI3Y9vk5xe5wUlFXyJ6AJ7lrR+enifUcxDVTxs0cB2+fyjBy6LFH CN/senF507MGaH82H8j5FqfaWWwPLiodYnrUl10DqQwuBzyB3f5UfCWYS okHtCwbGR/Ubq+nPk5AI5kEQICu8LrueWU/EaS5DNiunB2oLvHc3ODDdu A==;
X-IronPort-AV: E=Sophos;i="5.40,307,1496059200"; d="scan'208";a="163163475"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 10.6.2.2 - Outgoing - Outgoing
Received: from smtp.uoa.auckland.ac.nz (HELO uxcn13-ogg-a.UoA.auckland.ac.nz) ([10.6.2.2]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 04 Jul 2017 21:06:10 +1200
Received: from uxcn13-tdc-d.UoA.auckland.ac.nz (10.6.3.5) by uxcn13-ogg-a.UoA.auckland.ac.nz (10.6.2.2) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 4 Jul 2017 21:06:10 +1200
Received: from uxcn13-tdc-d.UoA.auckland.ac.nz ([fe80::6929:c5b:e4d6:fd92]) by uxcn13-tdc-d.UoA.auckland.ac.nz ([fe80::6929:c5b:e4d6:fd92%14]) with mapi id 15.00.1263.000; Tue, 4 Jul 2017 21:06:10 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Kristian Fiskerstrand <kristian.fiskerstrand@sumptuouscapital.com>
CC: "openpgp@ietf.org" <openpgp@ietf.org>
Thread-Topic: [FORGED] Re: [openpgp] Expiration impending: <draft-ietf-openpgp-rfc4880bis-01.txt>
Thread-Index: AQHS8sWFHqU4dlQfBk+AeHmoJilhxqJAOpqAgAAruwCAAU95AIAAANWAgAABvwCAAAGrAIAAAZCAgAFS0DP//3FRAIAA5ATV
Date: Tue, 4 Jul 2017 09:06:09 +0000
Message-ID: <1499159166033.35059@cs.auckland.ac.nz>
References: <149847732613.7086.8580563657011849337.idtracker@ietfa.amsl.com> <CALaySJKxWevOZYv1hOBFV-+3T=2x43vmie50t6ko2A+a-gTS_A@mail.gmail.com> <a3a82aab-a0d9-f044-21c0-26de346bf6b3@sixdemonbag.org> <20170702232541.t25v6mf36qnrxkex@genre.crustytoothpaste.net> <1b5da7bf-d43b-fde5-f6b6-28d9c6fd6edb@gmx.net> <94a05934-4b5c-4fb6-d127-beb0eacb47cf@sixdemonbag.org> <679411c5b2de4c308cbfbb3733c4fe54@usma1ex-dag1mb1.msg.corp.akamai.com> <9fbed93a-e4a7-3d00-1c53-ee587c2dface@o.banes.ch> <c51c709613184522815fa8838897dd2b@usma1ex-dag1mb1.msg.corp.akamai.com> <1499140902730.13818@cs.auckland.ac.nz>, <f1b3c9e5-ec8c-d4c2-2ccd-31fa65396440@sumptuouscapital.com>
In-Reply-To: <f1b3c9e5-ec8c-d4c2-2ccd-31fa65396440@sumptuouscapital.com>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/5_vV-iKMBWOQapqmUXM240Eo7FM>
Subject: Re: [openpgp] [FORGED] Re: Expiration impending: <draft-ietf-openpgp-rfc4880bis-01.txt>
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: Tue, 04 Jul 2017 09:06:15 -0000

Kristian Fiskerstrand <kristian.fiskerstrand@sumptuouscapital.com> writes:

>The most common complaint I'm hearing about OpenPGP is that it is too
>complex, as such I'm beginning to change my mind as to whether protocol
>agility is only a good thing, maybe we should work more on getting to
>consensus and reduce implementation complexity in order to make it possible
>for better auditing of implementations etc.

The easiest way to do that would be through a profile of 4880.  So instead of
opening up giant can of worms and trying to redo 4880 itself, where everyone
will want their own favourite change applied, publish a profile of 4880 with a
standard feature set for file encryption, email encryption, signed data, and
maybe one or two other things.  

For example for file encryption you might have MUST AES, MUST MDC, MUST
Iterated and Salted S2K (why do the other options even exist?), MUST either
five-octet or partial lengths... I think that's about it.  Then you can do PGP
file encryption in a pretty minimal amount of code rather than having to
include an entire protocol suite to deal with every obscure option in the
spec.

The profile option, rather than rewrite-the-RFC, is fully compatible with
existing implementations while allowing us to move forward on best-practice
mechanisms and ciphers and, above all, simplify implementation and testing.

Peter.