Re: [openpgp] Memory requirement for Argon2 (draft-06, sec 3.7.1.4)

Daniel Huigens <d.huigens@protonmail.com> Sat, 23 July 2022 15:49 UTC

Return-Path: <d.huigens@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 6E30AC159496 for <openpgp@ietfa.amsl.com>; Sat, 23 Jul 2022 08:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.com
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 XSpBmsud2k1m for <openpgp@ietfa.amsl.com>; Sat, 23 Jul 2022 08:49:09 -0700 (PDT)
Received: from mail-4322.protonmail.ch (mail-4322.protonmail.ch [185.70.43.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03CE4C157B54 for <openpgp@ietf.org>; Sat, 23 Jul 2022 08:49:08 -0700 (PDT)
Date: Sat, 23 Jul 2022 15:48:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1658591346; x=1658850546; bh=gTeuLehtMEIcwHluArb/Q67UT1JpTxdkiB29WfrS0FE=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=ulx5fQllz5VQjNeN/j0QJe2zQNFnbF6rK2UoINPgYo1fHePJHOALOoO4/+5ZLoWfb PHiXS49NbcIYsqO5cYd+nY16IDiq+8PfhzG4KCSqKAk/npQGGlbwvsLpiSvIWpVoUW Cwy4QTiQwS/tJCMe29J/x0xAIqg781aFfc8/kNyYvycbqTLCZQNZo91UVZPZwesdGK kXsdpNNRdM8p86nGDiEdfdRDJWaN8vni+Uo51Y5XlrtxZiIkxGsM9MiSlFdMHCqFfn cNiKGVwg61QOlNgrD0mzFKqZVLMhd6739whKZgadVYmGc2VIfJTtw9WG4ViOH3vLZT +9NVFQAw5nBpw==
To: Bruce Walzer <bwalzer@59.ca>
From: Daniel Huigens <d.huigens@protonmail.com>
Cc: Justus Winter <justus@sequoia-pgp.org>, openpgp@ietf.org
Reply-To: Daniel Huigens <d.huigens@protonmail.com>
Message-ID: <-wLiPGzfwzD-FfxAEf1bT1wRs3g4kD8IwoCFZRZ0sQ3tHaalhHBcasssC9urdqeTO_NcWH0xTh7GPpqYCY03VIhBe_ui2mLRrwAmkDUpKlw=@protonmail.com>
In-Reply-To: <YtsQXwmSSLm7f8tC@ohm.59.ca>
References: <YtHYPyDPY7nm5iSW@ohm.59.ca> <21Rcis4rNky_9wwR_P8GouVhsG9epEjx8lWh2xhTnpj2eTm1iFy-t3VoPTbNULXZEzX-dnTsk0DO_91EB0pUxjQrnVZy_cDJYaXv9utxYfQ=@protonmail.com> <YtlwBsk5qGIhEl7e@ohm.59.ca> <878rom1k3g.fsf@sequoia-pgp.org> <YtsQXwmSSLm7f8tC@ohm.59.ca>
Feedback-ID: 2934448:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/lcCLW2MFZK3WqzYhQfnnyuPsIZ0>
Subject: Re: [openpgp] Memory requirement for Argon2 (draft-06, sec 3.7.1.4)
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: Sat, 23 Jul 2022 15:49:13 -0000

You mention single-core performance leveling off, and then you mention
GPU/FPGA password crackers. That's indeed what causes the issue:
crackers using GPUs/FPGAs have a large advantage compared to users
using a single CPU core to hash their password. Memory-hard password
hashing algorithms like Argon2 aim to reduce this gap, by making
hashing using GPUs/FPGAs more expensive (and it also allows using
multiple cores to hash the password).

> The current question is: can Argon2 be adapted to provide some sort of
> practically usable improvement against those sorts of crackers in an
> OpenPGP environment.

Yes, I believe so. Do you have any concrete concerns why this might not
be the case?

Best,
Daniel