Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Uhff4-0002tI-Fd for bitcoin-development@lists.sourceforge.net; Wed, 29 May 2013 12:39:26 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.48 as permitted sender) client-ip=209.85.215.48; envelope-from=melvincarvalho@gmail.com; helo=mail-la0-f48.google.com; Received: from mail-la0-f48.google.com ([209.85.215.48]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Uhff3-0003Jh-8R for bitcoin-development@lists.sourceforge.net; Wed, 29 May 2013 12:39:26 +0000 Received: by mail-la0-f48.google.com with SMTP id fs12so8526004lab.21 for ; Wed, 29 May 2013 05:39:18 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.141.40 with SMTP id rl8mr1402314lbb.111.1369829660130; Wed, 29 May 2013 05:14:20 -0700 (PDT) Received: by 10.112.20.231 with HTTP; Wed, 29 May 2013 05:14:20 -0700 (PDT) In-Reply-To: References: Date: Wed, 29 May 2013 14:14:20 +0200 Message-ID: From: Melvin Carvalho To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a11c268a64b83f904ddda525f 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: 1Uhff3-0003Jh-8R Subject: Re: [Bitcoin-development] WebCryto standard to support secp256r1 but not 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: Wed, 29 May 2013 12:39:26 -0000 --001a11c268a64b83f904ddda525f Content-Type: text/plain; charset=ISO-8859-1 On 7 May 2013 12:18, Melvin Carvalho wrote: > Looking at the proposed native crypto browser support (should arrive in > the next year) > > http://www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dictionary > > We see: > > enum NamedCurve { > // NIST recommended curve P-256, also known as secp256r1. > "P-256", > // NIST recommended curve P-384, also known as secp384r1. > "P-384", > // NIST recommended curve P-521, also known as secp521r1. > "P-521" > }; > > I wonder if we might be able to get bitcoin's curve in there > > For more background on Koblitz curve used by bitcoin see: > > https://bitcointalk.org/?topic=2699.0 > Hi All I enuired about this and got the following reply, from the chair of the crypto group: [[ Just email public-webcrypto-comments@w3.org. It's a public list. Do definitely mention your use-cases! I think there's issues of whether NSS etc. already support it. I think the answer here is "no" but David can clarify. The goal is not to get browser vendors to write new crypto code, but to expose the crypto code that already exists. We still have an open issue about whether "experimental" registry for identifiers for say, new curves that aren't in the core spec, will be maintained. So, maybe if browsers don't support it today, it's always possible they might want to support it tomorrow given Bitcoin's growth. ]] Please let me know if anyone has a use case for ecdsa in the browser let me know. Or if anyone would like to write to the public list that's fine Otherwise I'll just fire off a mail and see what they come back with ... --001a11c268a64b83f904ddda525f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 7 May 2013 12:18, Melvin Carvalho <melvincarvalho@gmail= .com> wrote:
Looking = at the proposed native crypto browser support (should arrive in the next ye= ar)
We see:

enum NamedCurve {
=A0 // NIST recommended = curve P-256, also known as secp256r1.
=A0 "P-256",
=A0 // N= IST recommended curve P-384, also known as secp384r1.
=A0 "P-384&qu= ot;,
=A0 // NIST recommended curve P-521, also known as secp521r1.
=A0 "= P-521"
};

I wonder if we might be able to get bit= coin's curve in there

For more background on Koblitz = curve used by bitcoin see:

h= ttps://bitcointalk.org/?topic=3D2699.0

Hi All

I enuired about this and got the following re= ply, from the chair of the crypto group:

[[
Just email public-webcrypto-comments@w3.org. It's a public lis= t. Do definitely mention your use-cases!

I think there's issues of whether NSS etc. already support it. I think= =20 the answer here is "no" but David can clarify. The goal is not to= get=20 browser vendors to write new crypto code, but to expose the crypto code=20 that already exists.

We still have an open issue about whether "experimental" regi= stry=20 for identifiers for say, new curves that aren't in the core spec, will= =20 be maintained. So, maybe if browsers don't support it today, it's a= lways possible they might want to support it tomorrow given Bitcoin's growth= .
]]

Please let me know if anyone has a use case for e= cdsa in the browser let me know.

Or if anyone would like = to write to the public list that's fine

Otherwise I'll just fire off a mail and see what they co= me back with ...

--001a11c268a64b83f904ddda525f--