Re: [openpgp] [PATCH] RFC4880bis: Argon2i

Werner Koch <wk@gnupg.org> Tue, 03 November 2015 11:06 UTC

Return-Path: <wk@gnupg.org>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 419781ACE00 for <openpgp@ietfa.amsl.com>; Tue, 3 Nov 2015 03:06:23 -0800 (PST)
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
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 U4wYz9OCHVHn for <openpgp@ietfa.amsl.com>; Tue, 3 Nov 2015 03:06:21 -0800 (PST)
Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [IPv6:2001:aa8:fff1:100::22]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B65821B31F8 for <openpgp@ietf.org>; Tue, 3 Nov 2015 03:06:20 -0800 (PST)
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.80 #2 (Debian)) id 1ZtZPu-0007HK-Mm for <openpgp@ietf.org>; Tue, 03 Nov 2015 12:06:18 +0100
Received: from wk by vigenere.g10code.de with local (Exim 4.84 #3 (Debian)) id 1ZtZM9-0005It-7V; Tue, 03 Nov 2015 12:02:25 +0100
From: Werner Koch <wk@gnupg.org>
To: Nils Durner <ndurner@googlemail.com>
References: <5623AA95.4060903@googlemail.com>
Organisation: g10 Code GmbH
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
OpenPGP: id=F2AD85AC1E42B367; url=finger:wk@g10code.com
Mail-Followup-To: Nils Durner <ndurner@googlemail.com>, "openpgp\@ietf.org" <openpgp@ietf.org>
Date: Tue, 03 Nov 2015 12:02:25 +0100
In-Reply-To: <5623AA95.4060903@googlemail.com> (Nils Durner's message of "Sun, 18 Oct 2015 16:20:05 +0200")
Message-ID: <87k2pzwdku.fsf@vigenere.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/4XtYqSYx9I2-YckemdbwWPoEQIQ>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>
Subject: Re: [openpgp] [PATCH] RFC4880bis: Argon2i
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 03 Nov 2015 11:06:23 -0000

On Sun, 18 Oct 2015 16:20, ndurner@googlemail.com said:

> +Implementations MUST generate S2K specifiers that include salts
> +(either type 2, 3 or 4), as simple S2K specifiers are more vulnerable to

Type 2 is not defined but reserved, you probably meant type 1.

I also assume you allow type 1 (Salted S2K) to allow the use of an
entire random passphrase, right?  The salt then acts as IV for the SESK.
Should we explain this use of type 1?


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.