Re: [CFRG] Questions regarding draft-irtf-cfrg-hash-to-curve-10

Mike Hamburg <mike@shiftleft.org> Wed, 02 December 2020 22:32 UTC

Return-Path: <mike@shiftleft.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B28E43A15BA for <cfrg@ietfa.amsl.com>; Wed, 2 Dec 2020 14:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.305
X-Spam-Level:
X-Spam-Status: No, score=-1.305 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=shiftleft.org
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 RfseEoPHazt6 for <cfrg@ietfa.amsl.com>; Wed, 2 Dec 2020 14:32:16 -0800 (PST)
Received: from astral.shiftleft.org (unknown [54.219.126.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89F383A15E4 for <cfrg@ietf.org>; Wed, 2 Dec 2020 14:32:16 -0800 (PST)
Received: from [192.168.0.13] (unknown [37.228.237.57]) (Authenticated sender: mike) by astral.shiftleft.org (Postfix) with ESMTPSA id 972F7BB8F2; Wed, 2 Dec 2020 22:32:13 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shiftleft.org; s=sldo; t=1606948334; bh=W2zXyxuB6GbxyEopLyd+BMyJaANoWKeVzy4tIPd916w=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=inuNh8q4xCB72veoUD83no4k9nQcwvtGxz02/sWAH+5A/9u2oAEbT+5fTnKWHu9p8 wZW92pr3oIN7NQj1Q6e0pU20bIR1Rr1nfNvZAQjNZ6tgV0ks4Xw3dxNor9dh2TFZz/ oKGAkLn2+9XZ2HGT+kD6GwlpLoo0A3LRXtjRLXCo=
From: Mike Hamburg <mike@shiftleft.org>
Message-Id: <D8365079-6CA6-4C40-87D6-082322C8F187@shiftleft.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D14EC7AF-CD4B-4AB0-BA79-E1A9EB1F3B45"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
Date: Wed, 02 Dec 2020 22:32:11 +0000
In-Reply-To: <D6D24F48-6622-43E7-AE49-01DF864E521F@shiftleft.org>
Cc: Björn Haase <bjoern.haase@endress.com>, cfrg@ietf.org
To: Björn Haase <Bjoern.M.Haase@web.de>
References: <trinity-88ac791d-f437-4504-b9c8-57aa1119453b-1606942852142@3c-app-webde-bap34> <D6D24F48-6622-43E7-AE49-01DF864E521F@shiftleft.org>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/fG5QfqYAABdWakGCjfIauarpn0I>
Subject: Re: [CFRG] Questions regarding draft-irtf-cfrg-hash-to-curve-10
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2020 22:32:27 -0000

Sorry for the spam.  That should of course read “thanks editors!”.  — Mike


> On Dec 2, 2020, at 9:14 PM, Mike Hamburg <mike@shiftleft.org> wrote:
> 
> Great. The reference was accepted to ePrint remarkably quickly (eg hanks editors!), as
> 
> https://eprint.iacr.org/2020/1513 <https://eprint.iacr.org/2020/1513>
> 
> Cheers,
> — Mike
> 
>> On Dec 2, 2020, at 9:01 PM, Björn Haase <Bjoern.M.Haase@web.de> wrote:
>> 
>> 
>> Hi Mike,
>>  
>> thank you! That was exactly what I was looking for.  Once the paper gets on the eprints, I think that it should be added to the list of references in the Hash2Curve draft.
>>  
>> I'll be adding a corresponding feature request at the github repository.
>>  
>> Yours,
>>  
>> Björn.
>>  
>>  
>> Gesendet: Mittwoch, 02. Dezember 2020 um 14:36 Uhr
>> Von: "Mike Hamburg" <mike@shiftleft.org>
>> An: "Björn Haase" <bjoern.haase@endress.com>
>> Cc: "cfrg@ietf.org" <cfrg@ietf.org>
>> Betreff: Re: [CFRG] Questions regarding draft-irtf-cfrg-hash-to-curve-10
>> Hi Björn,
>>  
>> At some point (2013?) I wrote up an article on uniform hashing specifically for Elligator 2, but it got rejected for being too similar to previous work, and I never bothered to post it on ePrint.  I’ll do that now.  You can find proofs for two constructions in the paper cited below, one of which is hash-twice-and-add.
>>  
>> https://www.shiftleft.org/papers/indifferentiable/ <https://www.shiftleft.org/papers/indifferentiable/>
>>  
>> It may also be possible to show that Elligator 2 is well-distributed, but this paper shows directly that hash-twice-and-add works.
>>  
>> Cheers,
>> — Mike
>>  
>> PS: Mods, feel free to reject my previous attempt at this message, which is held because it has a PDF attached to it.
>>  
>> On Dec 2, 2020, at 11:58 AM, Björn Haase <bjoern.haase@endress.com <mailto:bjoern.haase@endress.com>> wrote:
>>  
>> Hello Riad, Hello Christopher,
>>  
>> As requested, I have filed an issue in the GIT draft regarding an update of our CPace security analysis.
>>  
>> I am currently reviewing one other aspect regarding the hash_to_curve construction, where the result of two mappings is added.
>>  
>> hash_to_curve(msg)
>> Input: msg, an arbitrary-length byte string.
>> Output: P, a point in G.
>>  
>> Steps: 
>> 1. u = hash_to_field(msg, 2)
>> 2. Q0 = map_to_curve(u[0])
>> 3. Q1 = map_to_curve(u[1])
>> 4. R = Q0 + Q1 # Point addition
>> 5. P = clear_cofactor(R)
>> 6. return P
>>  
>> The important aspect would be, that the result P comes from a uniform distribution.
>>  
>> I am aware of a result from Coron, Icart, brier and Madore “Efficient Indifferentiable Hashing into Ordinary Elliptic Curves.” where they saw the need for using rather something of the type of 
>> P = Q0 + x * Q1.
>>  
>> In “Indifferentiable Deterministic Hashing to Elliptic and Hyperelliptic Curves” there is a discussion that, even if uniformity could not be guaranteed, at least some weaker property of “well-distributed encodings” holds, which they show for SWU.
>>  
>> https://eprint.iacr.org/2010/539.pdf <https://eprint.iacr.org/2010/539.pdf>
>>  
>> I am having now the questions: Are you aware of a result that extends this to Elligator2? If I understood the paper correctly, the case of SSWU should be covered as part of the general properties of SWU. The guarantees seem to be linked to the property of the map that it is “well distributed” (where I did not yet understand the full implication of the character sums definition …).
>>  
>> Yours,
>>  
>> Björn.
>> Mit freundlichen Grüßen I Best Regards 
>> 
>> Dr. Björn Haase 
>> 
>> Senior Expert Electronics | TGREH Electronics Hardware
>> 
>> Endress+Hauser Liquid Analysis
>> 
>> Endress+Hauser Conducta GmbH+Co.KG | Dieselstrasse 24 | 70839 Gerlingen | Germany
>> Phone: +49 7156 209 377 | Fax: +49 7156 209 221
>> bjoern.haase@endress.com <mailto:bjoern.haase@endress.com> |  www.ehla.endress.com <http://www.ehla.endress.com/> 
>>  
>> Endress+Hauser Conducta GmbH+Co.KG
>> Amtsgericht Stuttgart HRA 201908
>> Sitz der Gesellschaft: Gerlingen
>> Persönlich haftende Gesellschafterin:
>> Endress+Hauser Conducta
>> Verwaltungsgesellschaft mbH
>> Sitz der Gesellschaft: Gerlingen
>> Amtsgericht Stuttgart HRA 201929
>> Geschäftsführer: Dr. Manfred Jagiella
>> 
>> Gemäss Datenschutzgrundverordnung sind wir verpflichtet, Sie zu informieren, wenn wir personenbezogene Daten von Ihnen erheben.
>> 
>> Dieser Informationspflicht kommen wir mit folgendem Datenschutzhinweis <https://www.de.endress.com/de/cookies-endress+hauser-website> nach.
>> 
>>  
>> Disclaimer: 
>> 
>> The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged
>> material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities
>> other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer.
>> This e-mail does not constitute a contract offer, a contract amendment, or an acceptance of a contract offer unless explicitly and conspicuously designated or stated as such.
>> 
>>  
>> _______________________________________________
>> CFRG mailing list
>> CFRG@irtf.org <mailto:CFRG@irtf.org>
>> https://www.irtf.org/mailman/listinfo/cfrg <https://www.irtf.org/mailman/listinfo/cfrg>_______________________________________________ CFRG mailing list CFRG@irtf.org https://www.irtf.org/mailman/listinfo/cfrg <https://www.irtf.org/mailman/listinfo/cfrg>_______________________________________________
> CFRG mailing list
> CFRG@irtf.org
> https://www.irtf.org/mailman/listinfo/cfrg