Re: [openpgp] SHA3 algorithm ids.
Phillip Hallam-Baker <phill@hallambaker.com> Sat, 08 August 2015 22:35 UTC
Return-Path: <hallam@gmail.com>
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 78FF11A1A7F for <openpgp@ietfa.amsl.com>; Sat, 8 Aug 2015 15:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 i21C3J4dtflB for <openpgp@ietfa.amsl.com>; Sat, 8 Aug 2015 15:35:27 -0700 (PDT)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FFBB1A1A15 for <openpgp@ietf.org>; Sat, 8 Aug 2015 15:35:27 -0700 (PDT)
Received: by lagz9 with SMTP id z9so38311233lag.3 for <openpgp@ietf.org>; Sat, 08 Aug 2015 15:35:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3E3/fzTGdbjYT7cGErJ8jyLJLo7mpSnpvBIKjkYZ6L4=; b=CN6WABfdN/IoNh3k89LTExzgLgb5CnNpfFdNOVd+k4nH0vR65AFCzAuYUg0iX7HmkY +gJK0/irGNLALTQ/xdqr22IZgdJyBp1wZgXLvtE6kJEidYJ7hrG5kLMxxjaqo0Z5wVvg yqJmdS5GYay/xnJ5HBrA3P2J0ChMYlrKfroz8Zcm65Dll6wsYab1fORqQW5tnV67zh+T +C4Hy/lwbNA/rBowdYMlDlpEHAqr0167aEDBd2tSv+ujNThuim5KZSvd6//UiYI3bYZp qefs52OPA8KD9isWyVsWdqeI1EF40QFErJ4Yhm+vbiFUBLhXgJ2+A366elr4shK/BePi zzJQ==
MIME-Version: 1.0
X-Received: by 10.112.12.233 with SMTP id b9mr14067411lbc.91.1439073325551; Sat, 08 Aug 2015 15:35:25 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.203.163 with HTTP; Sat, 8 Aug 2015 15:35:25 -0700 (PDT)
In-Reply-To: <55C681FC.9010100@iang.org>
References: <87y4hmi19i.fsf@vigenere.g10code.de> <7540C7A9-2830-4A63-8310-B684796DA279@nohats.ca> <55C681FC.9010100@iang.org>
Date: Sat, 08 Aug 2015 18:35:25 -0400
X-Google-Sender-Auth: iuu4UF41o0l4v5WO4x-q15rHdHU
Message-ID: <CAMm+LwhzO8-3Sf0UquCKQifFhauYPCUNCeTMwBUVBatdg3E_wg@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: ianG <iang@iang.org>
Content-Type: multipart/alternative; boundary="001a11c3b9de601832051cd45e10"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/5dppfOGyFLAlFoH7zuNO7RfjQ3s>
Cc: IETF OpenPGP <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: Sat, 08 Aug 2015 22:35:28 -0000
On Sat, Aug 8, 2015 at 6:26 PM, ianG <iang@iang.org> wrote: > On 8/08/2015 13:43 pm, Paul Wouters wrote: > >> What is the rationale to implement all sha3 variants? >> > > I agree, I'd like to see a really good rationale. > > I understand some protocols need lower grade versions for performance >> reasons but that seems to matter a lot less for openpgp usage. Why not just >> implement sha3-512? >> > > One would be good. Suits me to go for the longest one. > > How about this: > > > > ID Algorithm Text Name >>> -- --------- --------- >>> >> > snip > > 12 - RESERVED >>> 13 - RESERVED >>> 14 - RESERVED >>> 15 - SHA3-512 [FIPS202] "SHA3-512" >>> >> > > > And while we're at it, can we add DEPRECATED to all the rest except > SHA(2)512 ? Discussion in CFRG was definitely pointing to using 512 for the hash required for the internal bit. So if we choose one it should be 512 and truncate where necessary in the UI part.
- [openpgp] SHA3 algorithm ids. Werner Koch
- Re: [openpgp] SHA3 algorithm ids. Paul Wouters
- Re: [openpgp] SHA3 algorithm ids. Phillip Hallam-Baker
- Re: [openpgp] SHA3 algorithm ids. ianG
- Re: [openpgp] SHA3 algorithm ids. Phillip Hallam-Baker
- Re: [openpgp] SHA3 algorithm ids. ianG
- Re: [openpgp] SHA3 algorithm ids. Christoph Anton Mitterer
- Re: [openpgp] SHA3 algorithm ids. Phillip Hallam-Baker
- Re: [openpgp] SHA3 algorithm ids. ianG
- Re: [openpgp] SHA3 algorithm ids. Werner Koch
- Re: [openpgp] SHA3 algorithm ids. Peter Gutmann
- Re: [openpgp] SHA3 algorithm ids. Christoph Anton Mitterer
- Re: [openpgp] SHA3 algorithm ids. Stephen Farrell
- Re: [openpgp] SHA3 algorithm ids. ianG
- Re: [openpgp] SHA3 algorithm ids. Derek Atkins
- Re: [openpgp] SHA3 algorithm ids. Phillip Hallam-Baker
- Re: [openpgp] SHA3 algorithm ids. Werner Koch
- Re: [openpgp] SHA3 algorithm ids. ianG
- Re: [openpgp] SHA3 algorithm ids. Paul Wouters
- Re: [openpgp] SHA3 algorithm ids. Phillip Hallam-Baker
- Re: [openpgp] SHA3 algorithm ids. Peter Gutmann
- Re: [openpgp] SHA3 algorithm ids. Phillip Hallam-Baker
- [openpgp] Why or why not SHA{2,3}-512 (was: SHA3 … Werner Koch
- [openpgp] WWhy or why not SHA{2,3}-512 (was: SHA3… Werner Koch
- Re: [openpgp] SHA3 algorithm ids. Werner Koch
- Re: [openpgp] SHA3 algorithm ids. Werner Koch
- Re: [openpgp] SHA3 algorithm ids. Daniel Kahn Gillmor
- Re: [openpgp] SHA3 algorithm ids. Daniel Kahn Gillmor
- Re: [openpgp] SHA3 algorithm ids. Peter Gutmann
- [openpgp] SHA-x performance (was: SHA3 algorithm … Werner Koch
- Re: [openpgp] SHA-x performance (was: SHA3 algori… Daniel Kahn Gillmor
- Re: [openpgp] SHA-x performance (was: SHA3 algori… Peter Gutmann
- Re: [openpgp] SHA-x performance (was: SHA3 algori… Dang, Quynh
- Re: [openpgp] SHA-x performance Werner Koch
- Re: [openpgp] SHA3 algorithm ids. ianG
- Re: [openpgp] SHA-x performance Werner Koch
- Re: [openpgp] Why or why not SHA{2, 3}-512 (was: … Phillip Hallam-Baker
- Re: [openpgp] SHA-x performance Peter Gutmann
- Re: [openpgp] Why or why not SHA{2, 3}-512 Werner Koch
- Re: [openpgp] SHA-x performance ianG
- Re: [openpgp] SHA-x performance Phillip Hallam-Baker
- Re: [openpgp] SHA3 algorithm ids. Derek Atkins
- Re: [openpgp] SHA-x performance ianG
- Re: [openpgp] SHA3 algorithm ids. Phillip Hallam-Baker
- Re: [openpgp] SHA-x performance Bill Frantz
- Re: [openpgp] SHA-x performance Hilarie Orman
- Re: [openpgp] WWhy or why not SHA{2, 3}-512 (was:… Phillip Hallam-Baker
- Re: [openpgp] SHA-x performance NIIBE Yutaka
- Re: [openpgp] SHA3 algorithm ids. Derek Atkins
- Re: [openpgp] SHA-x performance Peter Gutmann
- Re: [openpgp] SHA3 algorithm ids. Bill Frantz
- Re: [openpgp] SHA3 algorithm ids. ianG
- Re: [openpgp] SHA3 algorithm ids. Derek Atkins
- Re: [openpgp] SHA3 algorithm ids. Bill Frantz
- Re: [openpgp] SHA3 algorithm ids. Phillip Hallam-Baker
- Re: [openpgp] SHA3 algorithm ids. Peter Gutmann
- Re: [openpgp] SHA3 algorithm ids. Andrey Jivsov
- Re: [openpgp] SHA3 algorithm ids. ianG
- Re: [openpgp] SHA3 algorithm ids. Robert J. Hansen
- Re: [openpgp] SHA3 algorithm ids. Werner Koch