Re: [Cfrg] Point format endian (was: Adoption of draft-ladd-spake2 as a RG document)

Peter Gutmann <> Mon, 26 January 2015 10:20 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 3B77D1A88A7 for <>; Mon, 26 Jan 2015 02:20:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ena2mayUDBzX for <>; Mon, 26 Jan 2015 02:20:40 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F13731A88A8 for <>; Mon, 26 Jan 2015 02:20:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=uoa; t=1422267639; x=1453803639; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=KoDHwuAncIrXp3wxMKGQY/aPafuZChqpKjDMSzwjzqg=; b=twbhYhK7alHoSxNBh9eeqTnSp0IF0nvWABgMw6qNtwRMjh7jPIJ84nLa e+t/MfI/jTSFjMqigCh7PrQWdk3AtEuAEJbc3WAkZpLEXjxSnQrldXj04 QFATP1Odazo8eLgLae63eGRGHBNVet1zvNI/X3Cy2vxqwUUDakBNJUtNK 4=;
X-IronPort-AV: E=Sophos;i="5.04,630,1406548800"; d="scan'208";a="303676154"
X-Ironport-Source: - Outgoing - Outgoing
Received: from ([]) by with ESMTP/TLS/AES256-SHA; 26 Jan 2015 23:20:36 +1300
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Mon, 26 Jan 2015 23:20:35 +1300
From: Peter Gutmann <>
To: "''" <>
Thread-Topic: [Cfrg] Point format endian (was: Adoption of draft-ladd-spake2 as a RG document)
Thread-Index: AdA5UbjGbnfzj1VITRalwzFEHlMbcA==
Date: Mon, 26 Jan 2015 10:20:34 +0000
Message-ID: <>
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: <>
Subject: Re: [Cfrg] Point format endian (was: Adoption of draft-ladd-spake2 as a RG document)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Crypto Forum Research Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 26 Jan 2015 10:20:43 -0000

Mike Hamburg <> writes:

>But will the endian complicate the implementation of the new curves?

Given that every single crypto bignum representation that I'm aware of (X.509,
S/MIME, PGP, SSH, TLS, OCSP, CMP, TSP, and many more) are all big-endian,
there are probably lots of crypto libraries that simply don't have little-
endian import/export routines.  Looking at BN_bn2bin()/BN_bin2bn() from one
widely-used library that powers half the Internet (and mobile phone market),
it only supports the big-endian format.  So that's automatic non-support for
the world's most widely-used crypto library outside of MS CryptoAPI (which
doesn't expose its bignum library).

I can't believe we're even having this endless discussion.  The universal
standard for external representations of bignums in IETF protocols is big-
endian.  Even the PGP and S/MIME, and SSH and TLS, folks have managed to agree
on that one.