IETF Logo Mail Archive

Re: [openpgp] AEAD Chunk Size

Bill Frantz <frantz@pwpconsult.com> Thu, 28 March 2019 18:54 UTC

Return-Path: <frantz@pwpconsult.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 BB67A12000F for <openpgp@ietfa.amsl.com>; Thu, 28 Mar 2019 11:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, URIBL_BLOCKED=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 ShKxUrH3CGGH for <openpgp@ietfa.amsl.com>; Thu, 28 Mar 2019 11:54:31 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) (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 3515F120313 for <openpgp@ietf.org>; Thu, 28 Mar 2019 11:54:26 -0700 (PDT)
Received: from [47.143.125.151] (helo=Williams-MacBook-Pro.local) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4) (envelope-from <frantz@pwpconsult.com>) id 1h9aAT-0002v0-0z; Thu, 28 Mar 2019 14:54:25 -0400
Date: Thu, 28 Mar 2019 11:54:23 -0700
From: Bill Frantz <frantz@pwpconsult.com>
To: Justus Winter <justuswinter@gmail.com>
cc: openpgp@ietf.org
X-Priority: 3
In-Reply-To: <878swzp4fb.fsf@europa.jade-hamburg.de>
Message-ID: <r480Ps-10143i-82BC5C540B764DDD8865CEC94C4A05A1@Williams-MacBook-Pro.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Mailsmith 2.4.3 (480)
X-ELNK-Trace: 3a5e54fa03f1b3e21aa676d7e74259b7b3291a7d08dfec79bbb8b28946efe7db03e133594f3c9b02350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 47.143.125.151
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/xsb1Qb8a6sdQ114iYu4k1rCnHA8>
Subject: Re: [openpgp] AEAD Chunk Size
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: Thu, 28 Mar 2019 18:54:34 -0000

On 3/28/19 at 5:30 AM, justuswinter@gmail.com (Justus Winter) wrote:

>For me, using an unbounded amount of memory is not an option for a
>component processing OpenPGP data if we want to build robust systems
>on top.

Can't you follow Jon's advice:

On 3/20/19 at 12:36 PM, joncallas=40icloud.com@dmarc.ietf.org 
(Jon Callas) wrote:

>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.

You can then treat any message that uses compression as 
malicious and refuse to process it.

Cheers - Bill

-------------------------------------------------------------------------
Bill Frantz        | When it comes to the world     | Periwinkle
(408)356-8506      | around us, is there any choice | 16345 
Englewood Ave
www.pwpconsult.com | but to explore? - Lisa Randall | Los Gatos, 
CA 95032

v2.23.0 | Report a Bug | By Email