IETF Logo Mail Archive

Re: [openpgp] OpenPGP encryption block modes (Was: The Argon2 proposal seems incomplete (Draft 6))

Bruce Walzer <bwalzer@59.ca> Fri, 26 August 2022 15:02 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 53EADC14CF1D for <openpgp@ietfa.amsl.com>; Fri, 26 Aug 2022 08:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 OkKv-imBNSlX for <openpgp@ietfa.amsl.com>; Fri, 26 Aug 2022 08:02:31 -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 8A504C14CE3B for <openpgp@ietf.org>; Fri, 26 Aug 2022 08:02:31 -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 1oRaqg-000Dqg-KX; Fri, 26 Aug 2022 10:02:18 -0500
Date: Fri, 26 Aug 2022 10:02:16 -0500
From: Bruce Walzer <bwalzer@59.ca>
To: Marcus Brinkmann <marcus.brinkmann@rub.de>
Cc: openpgp@ietf.org
Message-ID: <YwjgeAADJPbvdexE@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> <845A0B33-D115-4BA7-BD4D-ED76B72E0EB3@rub.de> <Yv/2F7+muV0/JPo4@watt.59.ca> <07340226-1E01-47AC-BB53-362E99D1288D@rub.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <07340226-1E01-47AC-BB53-362E99D1288D@rub.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/9Rn4uU0OXw0_NLaYJr-DsvCCGzU>
Subject: Re: [openpgp] OpenPGP encryption block modes (Was: The Argon2 proposal seems incomplete (Draft 6))
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: Fri, 26 Aug 2022 15:02:33 -0000

On Sat, Aug 20, 2022 at 03:38:45AM +0200, Marcus Brinkmann wrote:
[...]
> ... INT-CTXT ... INT-PTXT ...

If I could ask a favour...

I think this is the second time that I have seen these categories
applied to a discussion about SEIPD-MDC. The implication is that some
categories are inherently better than the others, but no context is
provided. Could we have more context here?

... and yes, I am aware there there is preexisting context out
there. What of it that I have stumbled across did not seem applicable
to a discussion involving SEIPD-MDC. Hence the request.

Bruce

v2.23.0 | Report a Bug | By Email