Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XdcRq-0005AM-QK for bitcoin-development@lists.sourceforge.net; Mon, 13 Oct 2014 10:01:50 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.172 as permitted sender) client-ip=209.85.217.172; envelope-from=melvincarvalho@gmail.com; helo=mail-lb0-f172.google.com; Received: from mail-lb0-f172.google.com ([209.85.217.172]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XdcRo-0006ir-G2 for bitcoin-development@lists.sourceforge.net; Mon, 13 Oct 2014 10:01:50 +0000 Received: by mail-lb0-f172.google.com with SMTP id b6so6154025lbj.31 for ; Mon, 13 Oct 2014 03:01:41 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.164.203 with SMTP id ys11mr2286313lbb.83.1413194497349; Mon, 13 Oct 2014 03:01:37 -0700 (PDT) Received: by 10.112.63.202 with HTTP; Mon, 13 Oct 2014 03:01:37 -0700 (PDT) In-Reply-To: References: Date: Mon, 13 Oct 2014 12:01:37 +0200 Message-ID: From: Melvin Carvalho To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a1133be8a035ef105054afcac X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (melvincarvalho[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XdcRo-0006ir-G2 Subject: [Bitcoin-development] Fwd: [Bug 24444] Named Curve Registry (adding secp256k1) X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2014 10:01:51 -0000 --001a1133be8a035ef105054afcac Content-Type: text/plain; charset=UTF-8 FYI: This is an issue I filed related to adding secp256k1 into Web Crypto API which will be implemented natively in (some) web browsers. If there is any feedback from crypto implementers, please feel free to add comments to this thread: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24444 ---------- Forwarded message ---------- From: Date: 13 October 2014 09:18 Subject: [Bug 24444] Named Curve Registry (adding secp256k1) To: melvincarvalho@gmail.com https://www.w3.org/Bugs/Public/show_bug.cgi?id=24444 Myron Davis changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |myrond@gmail.com Resolution|NEEDSINFO |--- --- Comment #2 from Myron Davis --- Could this be looked at again? Last response was waiting for feedback from crypto implementors. Currently secp256k1 is supported in the following SSL/TLS libraries now Botan NSS openssl LibreSSL PolarSSL JSSE The three other curves are all all have parameters which do not define how they were generated. secp256k1 curve has some great advantages in faster signature verification and how the values were determined for the curve. (i.e. not random). http://www.ietf.org/rfc/rfc4492 The curve has had a lot of eyes on it with lots of hardware and software supporting this curve. With discovery of backdoor's in NIST's random number generator (https://www.schneier.com/blog/archives/2007/11/the_strange_sto.html ) I would like to see a determined parameter curve instead of a "random" curve option. Thanks -- You are receiving this mail because: You reported the bug. --001a1133be8a035ef105054afcac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
FYI:

This is an issue I filed relat= ed to adding secp256k1 into Web Crypto API which will be implemented native= ly in (some) web browsers.

If there is any feedback= from crypto implementers, please feel free to add comments to this thread:= https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D24444
=

---------- Forwarded message -----= -----
From: <bugzilla@jessica.w3.org>
Date: 13 October 2014 09:18
Subject: [Bug 24444] Named Curve Regi= stry (adding secp256k1)
To: = melvincarvalho@gmail.com


https://www.w3.org/Bugs/P= ublic/show_bug.cgi?id=3D24444

Myron Davis <myrond@gmail.com>= ; changed:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0What=C2=A0 =C2=A0 |Removed=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|Added=
---------------------------------------------------------------------------= -
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Status|RESOLVED=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |REOPENED
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CC|=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 |myrond@gmail.com
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Resolution|NEEDSINFO=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|---

--- Comment #2 from Myron Davis <myr= ond@gmail.com> ---
Could this be looked at again?

Last response was waiting for feedback from crypto implementors.

Currently secp256k1 is supported in the following SSL/TLS libraries now
Botan
NSS
openssl
LibreSSL
PolarSSL
JSSE

The three other curves are all all have parameters which do not define how = they
were generated.=C2=A0 secp256k1 curve has some great advantages in faster s= ignature
verification and how the values were determined for the curve.=C2=A0 (i.e. = not
random).

http://www.ie= tf.org/rfc/rfc4492

The curve has had a lot of eyes on it with lots of hardware and software supporting this curve.

With discovery of backdoor's in NIST's random number generator
(https://www.schneier.com/blog/archives/2007/11/the_= strange_sto.html ) I would
like to see a determined parameter curve instead of a "random" cu= rve option.

Thanks

--
You are receiving this mail because:
You reported the bug.

--001a1133be8a035ef105054afcac--