IETF Logo Mail Archive

Re: [openpgp] Deprecating compression support

Bart Butler <bartbutler@protonmail.com> Fri, 22 March 2019 16:58 UTC

Return-Path: <bartbutler@protonmail.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 B087C1312C7 for <openpgp@ietfa.amsl.com>; Fri, 22 Mar 2019 09:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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=protonmail.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 0ANljRG55yef for <openpgp@ietfa.amsl.com>; Fri, 22 Mar 2019 09:58:36 -0700 (PDT)
Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch [185.70.40.132]) (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 32312131297 for <openpgp@ietf.org>; Fri, 22 Mar 2019 09:58:36 -0700 (PDT)
Date: Fri, 22 Mar 2019 16:58:27 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1553273913; bh=AcCUeXW3zB1upNMs1D8qdDXtgU0J0zaVWDjYXEOvlVI=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References: Feedback-ID:From; b=ANZmAVZR5ZQLFWnj8mmwaHTzsLC32HkC8Ei1vs5iTGEQ/LObQkSSF0u84iQ9q/zM0 OcUhhjbzpYcvLill/hZY9BMTZIYMJksCKhC5v1irdgc1PdqSMJrxfrJGjFzmuy14sE eFNI5+s9wRVBhNuRvWS63XeVc+1TwVLmCAUoKvOA=
To: Derek Atkins <derek@ihtfp.com>
From: Bart Butler <bartbutler@protonmail.com>
Cc: Andre Heinecke <aheinecke@gnupg.org>, "openpgp\\@ietf.org" <openpgp@ietf.org>, Justus Winter <justuswinter@gmail.com>
Reply-To: Bart Butler <bartbutler@protonmail.com>
Message-ID: <zcHmBrfRH1fe64PaV2E-pKgA-7bLEN81UY0epxKqKghLn42FyUQKxd-1XaCHsQ5m-bSk0Fji9Ppb38rosNCQlzt92LJu0tukrKLhh0nQCZc=@protonmail.com>
In-Reply-To: <sjmef6zouw9.fsf@securerf.ihtfp.org>
References: <871s3475dy.fsf@europa.jade-hamburg.de> <2181951.mQFCbn3PMz@esus> <xEPyX3yGpisVL1Tl_L1w_HI_zAAbfs3j9Itg0iZ_GxbxtkEoB_WJWvGjbHcdfb2BJx0rnIujUqVrFbIZNhUXWAGAm79B0fwHqoOiGxSk5tk=@protonmail.com> <87va0bxo50.fsf@wheatstone.g10code.de> <sjmef6zouw9.fsf@securerf.ihtfp.org>
Feedback-ID: XShtE-_o2KLy9dSshc6ANALRnvTQ9U24aqXW2ympbGschdpHbU6GYCTUCtfmGhY9HmOyP1Uweyandwh1AVDFrQ==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="---------------------66bb294df9105692f0d8a90dcde56d7b"; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/V3QcT16NU0jQ_oxQJW-o8PyGKbU>
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: Fri, 22 Mar 2019 16:58:40 -0000

+1 from me too, thanks!


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, March 22, 2019 7:17 AM, Derek Atkins <derek@ihtfp.com> wrote:

> +1 from me!
> Thanks, Werner.
> 

> -derek
> 

> Werner Koch wk@gnupg.org writes:
> 

> > So what about this minor change:
> > @@ -3322,8 +3321,9 @@ ## Compression Algorithms
> > 100--110 Private/Experimental algorithm
> > Implementations MUST implement uncompressed data. Implementations
> > -SHOULD implement ZIP. Implementations MAY implement any other
> > -algorithm.
> > +SHOULD implement ZLIB. For interoperability reasons implementations
> > +SHOULD be able to decompress using ZIP. Implementations MAY implement
> > +any other algorithm.
> > 

> > Hash Algorithms
> > 

> > ----------------
> > 

> > Salam-Shalom,
> > Werner
> 

> --
> 

>        Derek Atkins                 617-623-3745
>        derek@ihtfp.com             www.ihtfp.com
>        Computer and Internet Security Consultant
>

v2.23.0 | Report a Bug | By Email