From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XdjGy-0006aV-CP for bitcoin-development@lists.sourceforge.net; Mon, 13 Oct 2014 17:19:04 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bluematt.me designates 192.241.179.72 as permitted sender) client-ip=192.241.179.72; envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; Received: from mail.bluematt.me ([192.241.179.72]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1XdjGx-0001QX-3b for bitcoin-development@lists.sourceforge.net; Mon, 13 Oct 2014 17:19:04 +0000 Received: from [172.17.0.2] (gw.vpn.bluematt.me [162.243.132.6]) by mail.bluematt.me (Postfix) with ESMTPSA id 74A0A4F0AC for ; Mon, 13 Oct 2014 17:18:56 +0000 (UTC) Message-ID: <543C097D.7060308@bluematt.me> Date: Mon, 13 Oct 2014 17:18:53 +0000 From: Matt Corallo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.5 (-) 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 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1XdjGx-0001QX-3b Subject: Re: [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 17:19:04 -0000 See-also: this related bug on Curve25519 and some MS Research curves that generated far more discussion. https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839 Matt On 10/13/14 10:01, Melvin Carvalho wrote: > 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. > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://p.sf.net/sfu/Zoho > > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >