IETF Logo Mail Archive

Re: [openpgp] Deprecating compression support

Jon Callas <joncallas@icloud.com> Wed, 20 March 2019 19:36 UTC

Return-Path: <joncallas@icloud.com>
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 5A086130FC7 for <openpgp@ietfa.amsl.com>; Wed, 20 Mar 2019 12:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.45
X-Spam-Level:
X-Spam-Status: No, score=-3.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, KHOP_DYNAMIC=0.85, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=icloud.com
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 tBkdJR7JgFak for <openpgp@ietfa.amsl.com>; Wed, 20 Mar 2019 12:36:36 -0700 (PDT)
Received: from mr85p00im-ztdg06011101.me.com (mr85p00im-ztdg06011101.me.com [17.58.23.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABF61129508 for <openpgp@ietf.org>; Wed, 20 Mar 2019 12:36:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1553110596; bh=sSqagz25fqHmCQWwQLoxQH45Os3tY4uNpWrKoUD4t5A=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=mF8xaR3pNHqinI8yrOJXbeCieDlEpIfBDpWD9005nKuGtMgo5P6fVA43GtbpwioDv vzFHCqB+U7vEYVJbRCDsrN08xpiUlBu5HA+pzeTFjv5GNP1QZHBSUd8zQwRICyart5 iwumysX3IelUVx9JtlE9M9x9t80Nfk3E4705reKYBszMkrS8tpJY43gUJqWJC3z8JG ABlLLB9tREZWEU/ikYbJbeQPP3wlqG5Xdpa7Wnsw2RW9xrjhJRsU6KWdNoNnsyvN+c 27udEBlOI5cd0GLzrvNLrrJQ6Cbo7StFvgocz2+M1Jz9mA0JmhyqxhH2mUC2O7mtHV Yf++TO3VrkL+A==
Received: from [10.125.12.153] (67-207-120-150.static.wiline.com [67.207.120.150]) by mr85p00im-ztdg06011101.me.com (Postfix) with ESMTPSA id BC5484A0158; Wed, 20 Mar 2019 19:36:35 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Jon Callas <joncallas@icloud.com>
In-Reply-To: <2RAT852LYMAQD.3U70IQJPU0VPO@my.amazin.horse>
Date: Wed, 20 Mar 2019 12:36:34 -0700
Cc: Jon Callas <joncallas@icloud.com>, Andrey Jivsov <crypto@brainhub.org>, openpgp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0092256D-94EB-4FE5-9560-FEB0B8E3769E@icloud.com>
References: <CAKUk3bvBWoh9jz+T6t5yGs-P-P4cSg8AnSo_md3OFnzqVN-3=A@mail.gmail.com> <871s3475dy.fsf@europa.jade-hamburg.de> <96055353-B0EB-4E25-95CC-B25D9C5A0BA8@icloud.com> <2RAT852LYMAQD.3U70IQJPU0VPO@my.amazin.horse>
To: Vincent Breitmoser <look@my.amazin.horse>
X-Mailer: Apple Mail (2.3445.102.3)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-20_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1812120000 definitions=main-1903200142
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/A-qnkWPNUz-fzo5RFpZ1uqlP808>
Subject: Re: [openpgp] Deprecating compression support
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 20 Mar 2019 19:36:38 -0000


> On Mar 19, 2019, at 2:41 AM, Vincent Breitmoser <look@my.amazin.horse> wrote:
> 
> I'm unsure why both Jon and you think we need a slower "reasonable pace", when
> we have not only one but two very sharp points to make this cut as clean as can
> be? Both AEAD and the v5 key format already break compatibility. Why pull
> something over the edge that we want to phase out anyways?

I’m going to quibble over “two” and say that we have one — simplification of an overall implementation.

The second one has had comments on before. I’ll pick up some more in another missive relating to things people have said today.

To address your point, as I said in my long missive, you can do this today. No changes are needed to the protocol. All you have to do is put a compression preference on your key that says no compression, and then you won’t get compression. (Well, to be completely correct, if someone compresses then they’re non-compliant to the standard.) Repeating myself, I support and encourage implementations to do that by default.

Since you can do it today, there’s no need to rush. There are other people who have their own legitimate needs for it.

Does this make sense?

	Jon

v2.23.0 | Report a Bug | By Email