Re: [openpgp] SHA3 algorithm ids.

Werner Koch <wk@gnupg.org> Sun, 09 August 2015 07:55 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 83D111ACDF3 for <openpgp@ietfa.amsl.com>; Sun, 9 Aug 2015 00:55:37 -0700 (PDT)
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 HoPSkDhNV7S7 for <openpgp@ietfa.amsl.com>; Sun, 9 Aug 2015 00:55:32 -0700 (PDT)
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 5C1101ACDF2 for <openpgp@ietf.org>; Sun, 9 Aug 2015 00:55:32 -0700 (PDT)
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.80 #2 (Debian)) id 1ZOLS6-0005p5-7k for <openpgp@ietf.org>; Sun, 09 Aug 2015 09:55:30 +0200
Received: from wk by vigenere.g10code.de with local (Exim 4.84 #3 (Debian)) id 1ZOLMv-0002IT-AU; Sun, 09 Aug 2015 09:50:09 +0200
From: Werner Koch <wk@gnupg.org>
To: Paul Wouters <paul@nohats.ca>
References: <87y4hmi19i.fsf@vigenere.g10code.de> <7540C7A9-2830-4A63-8310-B684796DA279@nohats.ca>
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: Paul Wouters <paul@nohats.ca>, openpgp@ietf.org
Date: Sun, 09 Aug 2015 09:50:09 +0200
In-Reply-To: <7540C7A9-2830-4A63-8310-B684796DA279@nohats.ca> (Paul Wouters's message of "Sat, 8 Aug 2015 14:43:19 +0200")
Message-ID: <87egjcj3ym.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/i3nDwumjEp6JYpmViTBoI9atGuY>
Cc: openpgp@ietf.org
Subject: Re: [openpgp] SHA3 algorithm ids.
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: Sun, 09 Aug 2015 07:55:37 -0000

On Sat,  8 Aug 2015 14:43, paul@nohats.ca said:
> What is the rationale to implement all sha3 variants?

Because they are drop-in replacements for the 4 SHA2 algorithms; that is
the whole point of these algorithms.  Assigning algorithm ids does not
mean that they will be used - that is an entire different story.  It is
better to have well defined ids than to resort to experimental
algorithms.  FWIW, I do not plan to support them in write-mode.

Although IANA assigns them, we always agreed prior to any official
assignment on new algorithm ids.


Salam-Shalom,

   Werner

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