path: root/0e/8dd8d621400812b034536a386ee7d3e15ca5dc

Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <melvincarvalho@gmail.com>) id 1Xdxvj-000756-Ez
	for bitcoin-development@lists.sourceforge.net;
	Tue, 14 Oct 2014 08:58:07 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.175 as permitted sender)
	client-ip=209.85.217.175; envelope-from=melvincarvalho@gmail.com;
	helo=mail-lb0-f175.google.com; 
Received: from mail-lb0-f175.google.com ([209.85.217.175])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Xdxvh-0002M6-Pd
	for bitcoin-development@lists.sourceforge.net;
	Tue, 14 Oct 2014 08:58:07 +0000
Received: by mail-lb0-f175.google.com with SMTP id u10so7880586lbd.34
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 14 Oct 2014 01:57:59 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.243.39 with SMTP id wv7mr3875846lac.48.1413277079045;
	Tue, 14 Oct 2014 01:57:59 -0700 (PDT)
Received: by 10.112.63.202 with HTTP; Tue, 14 Oct 2014 01:57:58 -0700 (PDT)
In-Reply-To: <543C097D.7060308@bluematt.me>
References: <bug-24444-7046@http.www.w3.org/Bugs/Public/>
	<bug-24444-7046-xvP1kb2tHS@http.www.w3.org/Bugs/Public/>
	<CAKaEYhJPFoaSzPuGH80u3y6XoYCOpeQ0=3qote3jdwNVegoiVQ@mail.gmail.com>
	<543C097D.7060308@bluematt.me>
Date: Tue, 14 Oct 2014 10:57:58 +0200
Message-ID: <CAKaEYh+awWMF_7ExVkCVs5OLETDS4fPyC9NuY_LObGSPCHe7mA@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Matt Corallo <bitcoin-list@bluematt.me>
Content-Type: multipart/alternative; boundary=001a113433c8440d9005055e3695
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: 1Xdxvh-0002M6-Pd
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 14 Oct 2014 08:58:07 -0000

--001a113433c8440d9005055e3695
Content-Type: text/plain; charset=UTF-8

FYI:

"In order to progress towards exit to Last Call for the Web Crypto API, the
chair suggests the following resolution for that bug.

resolution : Bug CLOSED. This problem will be addressed by the extension bug
25618 https://www.w3.org/Bugs/Public/show_bug.cgi?id=25618.

If none objects before the 20th of Oct @20:00 UTC, this resolution will be
endorsed."

On 13 October 2014 19:18, Matt Corallo <bitcoin-list@bluematt.me> wrote:

> 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: ** <bugzilla@jessica.w3.org <mailto:bugzilla@jessica.w3.org>>
> > Date: 13 October 2014 09:18
> > Subject: [Bug 24444] Named Curve Registry (adding secp256k1)
> > To: melvincarvalho@gmail.com <mailto:melvincarvalho@gmail.com>
> >
> >
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=24444
> >
> > Myron Davis <myrond@gmail.com <mailto:myrond@gmail.com>> changed:
> >
> >            What    |Removed                     |Added
> >
> ----------------------------------------------------------------------------
> >              Status|RESOLVED                    |REOPENED
> >                  CC|                            |myrond@gmail.com
> > <mailto:myrond@gmail.com>
> >          Resolution|NEEDSINFO                   |---
> >
> > --- Comment #2 from Myron Davis <myrond@gmail.com
> > <mailto:myrond@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.  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
> >
>
>
> ------------------------------------------------------------------------------
> 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
>

--001a113433c8440d9005055e3695
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">FYI:<br><br>&quot;In order to progress towards exit to Las=
t Call for the Web Crypto API, the<br>
chair suggests the following resolution for that bug.<br>
<br>
resolution : Bug CLOSED. This problem will be addressed by the extension bu=
g<br>
25618 <a href=3D"https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D25618" ta=
rget=3D"_blank">https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D25618</a>.=
<br>
<br>
If none objects before the 20th of Oct @20:00 UTC, this resolution will be<=
br>
endorsed.&quot;</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 13 October 2014 19:18, Matt Corallo <span dir=3D"ltr">&lt;<a href=3D=
"mailto:bitcoin-list@bluematt.me" target=3D"_blank">bitcoin-list@bluematt.m=
e</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">See-also: this re=
lated bug on Curve25519 and some MS Research curves<br>
that generated far more discussion.<br>
<br>
<a href=3D"https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D25839" target=
=3D"_blank">https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D25839</a><br>
<br>
Matt<br>
<span class=3D""><br>
On 10/13/14 10:01, Melvin Carvalho wrote:<br>
&gt; FYI:<br>
&gt;<br>
&gt; This is an issue I filed related to adding secp256k1 into Web Crypto A=
PI<br>
&gt; which will be implemented natively in (some) web browsers.<br>
&gt;<br>
&gt; If there is any feedback from crypto implementers, please feel free to=
<br>
&gt; add comments to this thread:<br>
&gt; <a href=3D"https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D24444" tar=
get=3D"_blank">https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D24444</a><b=
r>
&gt;<br>
&gt; ---------- Forwarded message ----------<br>
</span><span class=3D"">&gt; From: ** &lt;<a href=3D"mailto:bugzilla@jessic=
a.w3.org">bugzilla@jessica.w3.org</a> &lt;mailto:<a href=3D"mailto:bugzilla=
@jessica.w3.org">bugzilla@jessica.w3.org</a>&gt;&gt;<br>
&gt; Date: 13 October 2014 09:18<br>
&gt; Subject: [Bug 24444] Named Curve Registry (adding secp256k1)<br>
</span><span class=3D"">&gt; To: <a href=3D"mailto:melvincarvalho@gmail.com=
">melvincarvalho@gmail.com</a> &lt;mailto:<a href=3D"mailto:melvincarvalho@=
gmail.com">melvincarvalho@gmail.com</a>&gt;<br>
&gt;<br>
&gt;<br>
&gt; <a href=3D"https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D24444" tar=
get=3D"_blank">https://www.w3.org/Bugs/Public/show_bug.cgi?id=3D24444</a><b=
r>
&gt;<br>
</span>&gt; Myron Davis &lt;<a href=3D"mailto:myrond@gmail.com">myrond@gmai=
l.com</a> &lt;mailto:<a href=3D"mailto:myrond@gmail.com">myrond@gmail.com</=
a>&gt;&gt; changed:<br>
<span class=3D"">&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 What=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|A=
dded<br>
&gt; ----------------------------------------------------------------------=
------<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Status|RESOLVED=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |REOPENED<br=
>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 CC|=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 |<a href=3D"mailto:myrond@gmail.com">myrond@gmail.com<=
/a><br>
</span>&gt; &lt;mailto:<a href=3D"mailto:myrond@gmail.com">myrond@gmail.com=
</a>&gt;<br>
<span class=3D"">&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Resolution|NEEDSINF=
O=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|---<=
br>
&gt;<br>
&gt; --- Comment #2 from Myron Davis &lt;<a href=3D"mailto:myrond@gmail.com=
">myrond@gmail.com</a><br>
</span>&gt; &lt;mailto:<a href=3D"mailto:myrond@gmail.com">myrond@gmail.com=
</a>&gt;&gt; ---<br>
<div><div class=3D"h5">&gt; Could this be looked at again?<br>
&gt;<br>
&gt; Last response was waiting for feedback from crypto implementors.<br>
&gt;<br>
&gt; Currently secp256k1 is supported in the following SSL/TLS libraries no=
w<br>
&gt; Botan<br>
&gt; NSS<br>
&gt; openssl<br>
&gt; LibreSSL<br>
&gt; PolarSSL<br>
&gt; JSSE<br>
&gt;<br>
&gt; The three other curves are all all have parameters which do not define=
<br>
&gt; how they<br>
&gt; were generated.=C2=A0 secp256k1 curve has some great advantages in fas=
ter<br>
&gt; signature<br>
&gt; verification and how the values were determined for the curve.=C2=A0 (=
i.e. not<br>
&gt; random).<br>
&gt;<br>
&gt; <a href=3D"http://www.ietf.org/rfc/rfc4492" target=3D"_blank">http://w=
ww.ietf.org/rfc/rfc4492</a><br>
&gt;<br>
&gt; The curve has had a lot of eyes on it with lots of hardware and softwa=
re<br>
&gt; supporting this curve.<br>
&gt;<br>
&gt; With discovery of backdoor&#39;s in NIST&#39;s random number generator=
<br>
&gt; (<a href=3D"https://www.schneier.com/blog/archives/2007/11/the_strange=
_sto.html" target=3D"_blank">https://www.schneier.com/blog/archives/2007/11=
/the_strange_sto.html</a> ) I<br>
&gt; would<br>
&gt; like to see a determined parameter curve instead of a &quot;random&quo=
t; curve option.<br>
&gt;<br>
&gt; Thanks<br>
&gt;<br>
&gt; --<br>
&gt; You are receiving this mail because:<br>
&gt; You reported the bug.<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div>&gt; ----------------------------------------------------------=
--------------------<br>
&gt; Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer<br>
&gt; Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Repor=
ts<br>
&gt; Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper<b=
r>
&gt; Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer<b=
r>
&gt; <a href=3D"http://p.sf.net/sfu/Zoho" target=3D"_blank">http://p.sf.net=
/sfu/Zoho</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Bitcoin-development mailing list<br>
&gt; <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
&gt; <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
&gt;<br>
<br>
---------------------------------------------------------------------------=
---<br>
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer<br>
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports<br=
>
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper<br>
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer<br>
<a href=3D"http://p.sf.net/sfu/Zoho" target=3D"_blank">http://p.sf.net/sfu/=
Zoho</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>

--001a113433c8440d9005055e3695--