Re: [openpgp] SHA3 algorithm ids.

Peter Gutmann <> Tue, 11 August 2015 16:39 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 226BE1ACD7A for <>; Tue, 11 Aug 2015 09:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cJHJSctcyfeH for <>; Tue, 11 Aug 2015 09:39:25 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C094F1ACD79 for <>; Tue, 11 Aug 2015 09:39:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=mail; t=1439311164; x=1470847164; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=a4BRpbiFly9zl2tt2QUEYMX6wjaF8McyJL2fBQ6Sz1k=; b=HFniPp1KhvknfmiTp1O92YZ5QbxdLEv3Nkzvtz4Qv5pxh3SUjhrT0wya AZvus9wHj9OGVNX+JlzOCP+rVkHdxRi+nkntn9DE3bnHVq9iZ2+d4YhLa nrTI9WcJ5qDpFY7lCjl+kK3JaeTM/JufCzwmxCyFzk7QDac7Ge7uwWoe0 Di6uBkzWXHedVy+AjkYZMOevnQ36UW6MAfTROuAulLaBJiuJkjCQEZRRH lDauUtbnpvLWv1C03MblVzKaF79l2sRQYXCrC8NDf6ui5inciXjd8LXIo YSy0IWFmS0srMR9LuBWG96KV7ms7p9wY33a7GJJEzega5jQTv+bYslYlF w==;
X-IronPort-AV: E=Sophos;i="5.15,654,1432555200"; d="scan'208";a="34432483"
X-Ironport-Source: - Outgoing - Outgoing
Received: from ([]) by with ESMTP/TLS/AES128-SHA; 12 Aug 2015 04:39:22 +1200
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Wed, 12 Aug 2015 04:39:22 +1200
From: Peter Gutmann <>
To: Daniel Kahn Gillmor <>, Phillip Hallam-Baker <>, Derek Atkins <>
Thread-Topic: [openpgp] SHA3 algorithm ids.
Thread-Index: AQHQ0bwwjUQponxgXEGSKRaVthfi2J4BQviAgACi0QCAA3eZy///kmAAgAHdvqr//2dhgIAAz/XS
Date: Tue, 11 Aug 2015 16:39:21 +0000
Message-ID: <>
References: <> <> <> <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Cc: IETF OpenPGP <>, ianG <>
Subject: Re: [openpgp] SHA3 algorithm ids.
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 11 Aug 2015 16:39:32 -0000

Daniel Kahn Gillmor <> writes:

>Is your concern CPU time or bandwidth (network/storage) or something else?


>If it's CPU time: on some architectures SHA-512 implementations are faster
>than SHA-256 implementations (except for digests of very short messages):

A huge number of devices, and in particular ones with less CPU power, are
still 32-bit, and will remain so for a long time, probably more or less

In addition from the original post it was unclear whether -512 referred to
SHA2 or SHA3 (which is why I qualified my reply as SHA2-256 and SHA3-512),
SHA3 will be ever worse than SHA2-512 in speed terms.

In terms of network/storage, there's the unnecessary use of 64-byte hashes
that I've already mentioned.  For TLS and SSH you really don't need more than
maybe 64 bits (not bytes), and certainly 64 bytes is nothing more than a
pointless waste of space when you're sending lots of small data quantities
back and forth.