Re: [Cfrg] 512-bit twisted Edwards curve and curve generation methods in Russian standardization
Alyssa Rowan <akr@akr.io> Wed, 28 January 2015 18:04 UTC
Return-Path: <akr@akr.io>
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 6E1941A86FE for <cfrg@ietfa.amsl.com>; Wed, 28 Jan 2015 10:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 jwMqBs7HV5xe for <cfrg@ietfa.amsl.com>; Wed, 28 Jan 2015 10:04:33 -0800 (PST)
Received: from entima.net (entima.net [78.129.143.175]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A62D1A6F29 for <cfrg@irtf.org>; Wed, 28 Jan 2015 10:04:33 -0800 (PST)
Message-ID: <54C924AC.7060504@akr.io>
Date: Wed, 28 Jan 2015 18:04:28 +0000
From: Alyssa Rowan <akr@akr.io>
MIME-Version: 1.0
To: "Stanislav V. Smyshlyaev" <smyshsv@gmail.com>, "cfrg@irtf.org" <cfrg@irtf.org>
References: <CAMr0u6=prmjMv7e+S5UAGVw+uCQWPk-f86Koa04GVx8CZs4J4Q@mail.gmail.com> <C877C13D-0178-4BDD-BC58-4E7C417600D1@akr.io> <CAMr0u6=pgV8P19zoEbztCas20XX68V40wN-3qwrbqAxQeMpJQg@mail.gmail.com>
In-Reply-To: <CAMr0u6=pgV8P19zoEbztCas20XX68V40wN-3qwrbqAxQeMpJQg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/cfrg/icsGtmmnZEMDYioDfOF4sx6r5N4>
Subject: Re: [Cfrg] 512-bit twisted Edwards curve and curve generation methods in Russian standardization
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 18:04:36 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 28/01/2015 14:14, Stanislav V. Smyshlyaev wrote: > …one has either to combine such algebraic properties of a curve > with properties of a hash function (for a trivial example, to have > an ability to obtain a hash preimage) or to choose a very probable > "backdoor-type" property of a curve (such that it is possible to > obtain by random choice of a curve). Even a _partial_ second-preimage presents a significant problem here, which is the big problem with the SEC1/NIST approach - and unless I'm misunderstanding of course, the one you've taken? A simple brute force partial second-preimage search lets you cook a seed which yields a hash (even with a theoretical perfect hash function) with as many bits as you can brute-force (64, no problem; 70-80, maybe for some?), and thus covertly select curves with properties one desires (and perhaps, which we don't desire!) even down to, say, p=1/(2^63). Now I wouldn't characterise those properties as "very probable" to occur by random chance at all, or indeed a large class - but it's definitely a totally feasible condition to force for anyone who gets to freely choose the seed. That's why our draft rigid generation process doesn't use seeds - and why anyone who does use seeds needs to be incredibly careful to the extent to which anyone _can_ choose them (BADA55 being a demonstration that a 'verifiably pseudo-random' process needs to be careful too, as the mere choice of primitives and constants in the process may allow enough of a degree of freedom to affect the outcome to force a one-in-a-million choice). So… who did choose W? Or, if W is a hash output itself, who chose the seed for that? (The attack still works on iterated hash functions.) - -- /akr -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJUySSsAAoJEOyEjtkWi2t6HKIP/1OfbTbsADv0gUI2cywXmINM 2WTc3ulsMMEPDI/LIp15Dg8BEZJHQAiUWpZGcRGAvPyX6X27Uo+Jol2+Ab2G/EAh zRLkw0HKnaACGpJftLKDoOZmwa2myLJWjVANz3YhRqu9HOee+IbPO1nelQMVJn89 hEg7h/JcPHQT65/PuXDE5ZVCwbJSfth3/LxS0bmkLeC1hGdr+bHuhPvf298vtk+d ZlcmL5oiexCs+2Io63U6CTL9+XT881su75aMfMK+8cW9SphV6IASocSmhPotAJns blYCnvBxAKNZD5cgHlgx7TV/9bhO14n8AT7ausUT6cwLzRj6kJT6fsBreeiNZagy SC2j6WOFYgThyGbUz6xoot/bHpmP0zGVxeQwKmTIVjlD4IHmSA7dpf2wCCJSkkhI DYfc7bAPKOl2+DXn43DRJ6uyGAOfpU+/oKkzUzyIklhP/7B17F1PBNMKVIgySKtC ccozug5LNcwHfuzxpJVITDR9YvAwxDkcGuD0dVetaH4wY/F/4n2YWqhqQd7PTZgk NtO0HhsoL610CpfVrB1PsIHvPWRwt8pAzi3k0oJMxjg7PB1bmVMj6Xv/BctvA4ki BDiMKr9k9ZCSgwlFxkQR3568v993g72vUh6NwbSfChqxvZBcKnx1MayF8wQhjC96 FtOdtZJ9NDzZlO0QNbvw =gvRr -----END PGP SIGNATURE-----
- [Cfrg] 512-bit twisted Edwards curve and curve ge… Станислав Смышляев
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Paterson, Kenny
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Stanislav V. Smyshlyaev
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Alyssa Rowan
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Stanislav V. Smyshlyaev
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Tony Arcieri
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Paul Hoffman
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Watson Ladd
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Tony Arcieri
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Stanislav V. Smyshlyaev
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Paul Hoffman
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Alyssa Rowan
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Tony Arcieri
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Stanislav V. Smyshlyaev
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… Stanislav V. Smyshlyaev
- Re: [Cfrg] 512-bit twisted Edwards curve and curv… CodesInChaos