Re: [openpgp] AEAD Chunk Size

Tobias Mueller <muelli@cryptobitch.de> Mon, 18 March 2019 09:49 UTC

Return-Path: <muelli@cryptobitch.de>
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 14527128CE4 for <openpgp@ietfa.amsl.com>; Mon, 18 Mar 2019 02:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 WD6m5NxJ2vYU for <openpgp@ietfa.amsl.com>; Mon, 18 Mar 2019 02:49:27 -0700 (PDT)
Received: from bitbox.cryptobit.ch (cryptobit.ch [188.40.138.131]) (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 13571128B33 for <openpgp@ietf.org>; Mon, 18 Mar 2019 02:49:26 -0700 (PDT)
Received: from unibox.fritz.box (p5B0F5932.dip0.t-ipconnect.de [91.15.89.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.cryptobit.ch (Postfix) with ESMTPSA id 44NBGq14TTz13C3b; Mon, 18 Mar 2019 10:49:23 +0100 (CET)
Message-ID: <13a5e06b512120ebf2d04b9a018f5eb6a0457d42.camel@cryptobitch.de>
From: Tobias Mueller <muelli@cryptobitch.de>
To: "Neal H. Walfield" <neal@walfield.org>, openpgp@ietf.org
Date: Mon, 18 Mar 2019 10:49:22 +0100
In-Reply-To: <87mum6ekbd.wl-neal@walfield.org>
References: <87mumh33nc.wl-neal@walfield.org> <871s3qd4yg.fsf@wheatstone.g10code.de> <87mum6ekbd.wl-neal@walfield.org>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/5cSY_CvlRwQaj5rWFEewy-PnjAA>
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: Mon, 18 Mar 2019 09:49:29 -0000

Hi,

On Thu, 2019-03-07 at 17:11 +0100, Neal H. Walfield wrote:
> > Let me repeat it again: The chunking was introduced for just one
> > purpose: To be able to detect rare transmission errors earlier than
> > at
> > the end of the message.
> 
> I agree that AEAD helps detect transmission errors earlier.  But, AEAD
> does so much more than that.  In particular, it prevents attacks like
> EFAIL.  It seems to me that it's worth adapting to this new threat.
I have the feeling that this is the spot where we are close to hitting
the underlying misunderstanding.

AFAICS, Werner is talking about chunking. You are talking about AEAD. I
have the feeling that it's helpful for the discussion to carefully
distinguish those.

You seem to imply that any chunked scheme is proper AEAD. But that's not
true. It's not difficult to make a scheme with chunks, and the spec
probably has already done so, but it's not trivial.

Cheers,
  Tobi