IETF Logo Mail Archive

Re: [Cfrg] Point format endian

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 28 January 2015 01:24 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A2A1A0235 for <cfrg@ietfa.amsl.com>; Tue, 27 Jan 2015 17:24:52 -0800 (PST)
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 UoezVDiI_rq8 for <cfrg@ietfa.amsl.com>; Tue, 27 Jan 2015 17:24:51 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B49061A0210 for <cfrg@irtf.org>; Tue, 27 Jan 2015 17:24:50 -0800 (PST)
Received: by mail-lb0-f178.google.com with SMTP id u10so16157288lbd.9 for <cfrg@irtf.org>; Tue, 27 Jan 2015 17:24:49 -0800 (PST)
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=0wANuxMOs5Iry5nYzFNvqh1xlme1XdWrpzUG5+c8wK4=; b=DSrRzXCU9ekokt+78DD86zePHdGGsSkP2pWRcID3EFBS4odDtNgq9forDyOSQkL7KQ y0VsiqdcJKsRIv2VwXVoVxKCONv8IjyLHuxgHfVOqLq2KAkOHCKYrSWneT3+caZMW/8S 19jJMqU6sLluRCdFP8UKc7NaFnNQ2ajxJLeUXmwQ1CKWfBy9frGgCfV7ZxJol3rhhR0S L2BJfLlg3ImpPhz3OtAvvzRjVTH3DXdLO0LjLRxJbX7GZkUpZIlbE5nVvWB6YLqUw0gg i0SGwqyh/NWWftXJghVDl5FvgAGgsXtR60v6TGFYAMxpBwL2MUNS+wAMmsQLMqFlMqBx 7z9g==
MIME-Version: 1.0
X-Received: by 10.152.87.50 with SMTP id u18mr4993602laz.21.1422408289087; Tue, 27 Jan 2015 17:24:49 -0800 (PST)
Sender: hallam@gmail.com
Received: by 10.112.147.193 with HTTP; Tue, 27 Jan 2015 17:24:48 -0800 (PST)
In-Reply-To: <54C7B572.2020109@cs.tcd.ie>
References: <9A043F3CF02CD34C8E74AC1594475C73AAF68325@uxcn10-tdc05.UoA.auckland.ac.nz> <54C76EED.6090205@cs.tcd.ie> <sjm386wjko8.fsf@securerf.ihtfp.org> <b2b8d964885246748ebde894064b6a3c@ustx2ex-dag1mb2.msg.corp.akamai.com> <54C7B572.2020109@cs.tcd.ie>
Date: Tue, 27 Jan 2015 20:24:48 -0500
X-Google-Sender-Auth: 6DV2p_PIc_14ZgLz7fN_-BqdtuU
Message-ID: <CAMm+LwgZP60ypKSAgLop0CGykPPsMo2pUR+gPgYf3Zc2PPuhsw@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="001a11c36536cbf7e8050dac3c4b"
Archived-At: <http://mailarchive.ietf.org/arch/msg/cfrg/XOhwI05EN_AFsZEs-Y3gdRvdZ5U>
Cc: "cfrg@irtf.org" <cfrg@irtf.org>, Peter Gutmann <pgut001@cs.auckland.ac.nz>
Subject: Re: [Cfrg] Point format endian
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 01:24:52 -0000

On Tue, Jan 27, 2015 at 10:57 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie
> wrote:

>
>
> On 27/01/15 15:46, Salz, Rich wrote:
> > Don't they have a different code path for the math implementation?
>
> Right. So it makes very little to no difference really I'd guess.
>
> Or if someone has code where it would then sending a pointer to
> that would help me at least. Anytime I've done that kind of code
> it'd have been no problem at all to deal with this issue.
>

Actually no, it makes a huge difference because I only have one encoder
library that serves all my algorithms and that maps the in-memory data
formats to one serialization format.

The algorithm implementations don't have their own bignum implementations
either. This is a different layer in the application stack, different rules
apply.

v2.23.0 | Report a Bug | By Email