Re: [openpgp] OpenPGP encryption block modes

Bruce Walzer <bwalzer@59.ca> Wed, 10 August 2022 14:53 UTC

Return-Path: <bwalzer@59.ca>
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 AD8B9C15AD22 for <openpgp@ietfa.amsl.com>; Wed, 10 Aug 2022 07:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khYM7tTzb2Jo for <openpgp@ietfa.amsl.com>; Wed, 10 Aug 2022 07:53:51 -0700 (PDT)
Received: from mail.59.ca (mail.59.ca [205.200.229.83]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA512) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63752C14F734 for <openpgp@ietf.org>; Wed, 10 Aug 2022 07:53:50 -0700 (PDT)
Received: from [104.246.140.18] (helo=watt.59.ca) by mail.59.ca with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <bwalzer@59.ca>) id 1oLn5K-000OAY-0t; Wed, 10 Aug 2022 09:53:26 -0500
Date: Wed, 10 Aug 2022 09:53:23 -0500
From: Bruce Walzer <bwalzer@59.ca>
To: Werner Koch <wk@gnupg.org>
Cc: Daniel Huigens <d.huigens@protonmail.com>, justus@sequoia-pgp.org, openpgp@ietf.org
Message-ID: <YvPGY8ArcKD7Hr1p@watt.59.ca>
References: <87edy7keb6.fsf@thinkbox> <YuFc+w02FiRQmHcg@watt.59.ca> <87bktajjvq.fsf@thinkbox> <YuKpxp0/Dy1DfC19@watt.59.ca> <875yjhjg2c.fsf@thinkbox> <87r124m64c.fsf@wheatstone.g10code.de> <YulX9jI1+wOCwLJq@ohm.59.ca> <Q6EUpbQm0e5f1OiU-77Old9p9FXyLCaFZ8pMm7PTt8VTLQJaXRQzWIDSwc3db6yI-56imyOaTNdt9TC8Zrm1jN_kPKxFYH4OqEu6o-Wfquo=@protonmail.com> <YuvlHdLz0Sfle7Ot@ohm.59.ca> <87a68ji1bv.fsf@wheatstone.g10code.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <87a68ji1bv.fsf@wheatstone.g10code.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/u_ZwPhMY0u9UknfCqDlfRoCHcYI>
Subject: Re: [openpgp] OpenPGP encryption block modes
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
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, 10 Aug 2022 14:53:55 -0000

On Fri, Aug 05, 2022 at 09:41:56AM +0200, Werner Koch wrote:
> On Thu,  4 Aug 2022 10:26, Bruce Walzer said:
> 
> > I thought you guys were mostly doing messaging. Why would performance
> > be important in that environment? Speaking of messaging, wouldn't you
> 
> A major use case is to encrypt bulk data in the range for hundreds of
> GiByte and often up to several TiByte.  And that is not only for
> backups.  It matters whether it takes 6 hours or 45 minutes.

That raises a question for me as I hold the position that OpenPGP does
not need any more block cipher modes. I had the impression that
SEIP-MDC (OCFB-MDC) would be relatively fast as the slow part is
SHA1. SHA1 is one of the faster cryptographic hashes and is hardware
accelerated on common platforms. I assumed that the slowness was
because no one had ever bothered to optimize things. Is this true?

> 
> Actually this is also the reason why we came up with the chunked OCB
> mode - to detect those rare transmission errors more early.

I would really like to comment on this, but I keep getting stuck on
the image of encrypted data running through netcat. Would you be so
kind as to provide a definite use case?

Bruce