IETF Logo Mail Archive

Re: [openpgp] New S2K specifiers?

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Mon, 01 April 2019 04:02 UTC

Return-Path: <dkg@fifthhorseman.net>
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 BF2D7120005 for <openpgp@ietfa.amsl.com>; Sun, 31 Mar 2019 21:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.458
X-Spam-Level:
X-Spam-Status: No, score=-0.458 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b=gdLoa06f; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b=FQiwDJjL
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 xjB0XflGRf_C for <openpgp@ietfa.amsl.com>; Sun, 31 Mar 2019 21:02:30 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E045120072 for <openpgp@ietf.org>; Sun, 31 Mar 2019 21:02:29 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1554091348; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : content-transfer-encoding : from; bh=kRpwJ2GuCK2JDmGQCg9C/UX61iG+ltiBFCerfw2/Xug=; b=gdLoa06fHLzFxwbP+y3ACuuP/2nlu5GbnxrAQQx3jelKyzb7HERUUS0Q PMU9kyf39VordFUrl4xieTvQr5n7CA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1554091348; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : content-transfer-encoding : from; bh=kRpwJ2GuCK2JDmGQCg9C/UX61iG+ltiBFCerfw2/Xug=; b=FQiwDJjLJcAPwQQ+kwnP4ENMLM6Pt3kvlhEpNBfLjV7iWf62z6kYODYd YpNmkmaN2xcvl5GMlgWXffvk2dt6f8+V/O3w3UVaFhKEFotkPjCKHTSXzH KBGD+8sS37en1oXZ13Mog4KAvkMuym2xA0Y6mD0/VDueTwy/ui2yn9YdHf Ekc270185C8XdO/oTddf8+dttsGDWO2dEIc52LENq4EvLFRZwrnI+Z5+zw PpgAX6R1iosmPf5ZNxNBnNj1H0j5zVfO9Bf3/GjsO0MnE04AygOgipXmpl mB+QgSFxsjpGDcxFRJm3wFiOgYlD0n0q3hU0QzlFUQ8Eomju8N2+yg==
Received: from fifthhorseman.net (ool-6c3a0662.static.optonline.net [108.58.6.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 17244F9A7 for <openpgp@ietf.org>; Mon, 1 Apr 2019 00:02:28 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id A67E920BEA; Sun, 31 Mar 2019 17:37:07 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: openpgp@ietf.org
In-Reply-To: <20190331121024.cgta3emx6vefex6x@aurora.local.incenp.org>
References: <20190331121024.cgta3emx6vefex6x@aurora.local.incenp.org>
Autocrypt: addr=dkg@fifthhorseman.net; prefer-encrypt=mutual; keydata= mDMEXEK/AhYJKwYBBAHaRw8BAQdAr/gSROcn+6m8ijTN0DV9AahoHGafy52RRkhCZVwxhEe0K0Rh bmllbCBLYWhuIEdpbGxtb3IgPGRrZ0BmaWZ0aGhvcnNlbWFuLm5ldD6ImQQTFggAQQIbAQUJA8Jn AAULCQgHAgYVCgkICwIEFgIDAQIeAQIXgBYhBMS8Lds4zOlkhevpwvIGkReQOOXGBQJcQsbzAhkB AAoJEPIGkReQOOXG4fkBAO1joRxqAZY57PjdzGieXLpluk9RkWa3ufkt3YUVEpH/AP9c+pgIxtyW +FwMQRjlqljuj8amdN4zuEqaCy4hhz/1DbgzBFxCv4sWCSsGAQQB2kcPAQEHQERSZxSPmgtdw6nN u7uxY7bzb9TnPrGAOp9kClBLRwGfiPUEGBYIACYWIQTEvC3bOMzpZIXr6cLyBpEXkDjlxgUCXEK/ iwIbAgUJAeEzgACBCRDyBpEXkDjlxnYgBBkWCAAdFiEEyQ5tNiAKG5IqFQnndhgZZSmuX/gFAlxC v4sACgkQdhgZZSmuX/iVWgD/fCU4ONzgy8w8UCHGmrmIZfDvdhg512NIBfx+Mz9ls5kA/Rq97vz4 z48MFuBdCuu0W/fVqVjnY7LN5n+CQJwGC0MIA7QA/RyY7Sz2gFIOcrns0RpoHr+3WI+won3xCD8+ sVXSHZvCAP98HCjDnw/b0lGuCR7coTXKLIM44/LFWgXAdZjm1wjODbg4BFxCv50SCisGAQQBl1UB BQEBB0BG4iXnHX/fs35NWKMWQTQoRI7oiAUt0wJHFFJbomxXbAMBCAeIfgQYFggAJhYhBMS8Lds4 zOlkhevpwvIGkReQOOXGBQJcQr+dAhsMBQkB4TOAAAoJEPIGkReQOOXGe/cBAPlek5d9xzcXUn/D kY6jKmxe26CTws3ZkbK6Aa5Ey/qKAP0VuPQSCRxA7RKfcB/XrEphfUFkraL06Xn/xGwJ+D0hCw==
Date: Sun, 31 Mar 2019 17:37:07 -0400
Message-ID: <87k1gebu9o.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/8POBP6RfagskoBmb2rSsb7L_dCw>
Subject: Re: [openpgp] New S2K specifiers?
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, 01 Apr 2019 04:02:32 -0000

On Sun 2019-03-31 13:10:24 +0100, Damien Goutte-Gattat wrote:
> * Is there any interest for a “more modern” S2K, or is the
>   Iterated+Salted S2K still considered fine enough for RFC4880bis?

I think having argon2i included in rfc4880bis would be concretely
useful; iterated+salted hasn't been the best practice for S2K for well
over a decade.

The main argument i can imagine against it is if no OpenPGP
implementation has any plans or desire to implement it, or if there are
specific objections related to IPR.

I would like to hear from people who think rfc4880bis should not include
a winner of the PHC, if the goal is a cryptographic refresh.

      --dkg

v2.23.0 | Report a Bug | By Email