1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <melvincarvalho@gmail.com>) id 1VsG8k-0007i8-DJ
for bitcoin-development@lists.sourceforge.net;
Sun, 15 Dec 2013 18:10:06 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.182 as permitted sender)
client-ip=209.85.223.182; envelope-from=melvincarvalho@gmail.com;
helo=mail-ie0-f182.google.com;
Received: from mail-ie0-f182.google.com ([209.85.223.182])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VsG8i-0006Ru-Vw
for bitcoin-development@lists.sourceforge.net;
Sun, 15 Dec 2013 18:10:06 +0000
Received: by mail-ie0-f182.google.com with SMTP id as1so5427349iec.27
for <bitcoin-development@lists.sourceforge.net>;
Sun, 15 Dec 2013 10:09:59 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.13.9 with SMTP id d9mr12119571igc.25.1387130999673; Sun,
15 Dec 2013 10:09:59 -0800 (PST)
Received: by 10.64.226.233 with HTTP; Sun, 15 Dec 2013 10:09:59 -0800 (PST)
Date: Sun, 15 Dec 2013 19:09:59 +0100
Message-ID: <CAKaEYh+=cFKzwW7J9j6Bz4P6OxTC56k3K1fFG4svg843QRTjVA@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: public-webcrypto-comments@w3.org
Content-Type: multipart/alternative; boundary=089e013c68e27e64e304ed969a89
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
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: bitcointalk.org]
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: 1VsG8i-0006Ru-Vw
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Web Crypto -- Named Curve Dictionary (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: Sun, 15 Dec 2013 18:10:06 -0000
--089e013c68e27e64e304ed969a89
Content-Type: text/plain; charset=ISO-8859-1
Harry and David suggested I send a message to this group. I was wondering
if the crypto group may consider adding support for *secp256k1* in the
browser Named Curve dictionary.
http://www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dictionary
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"
};
Over the last year, there has been a significant increase in deployment for
this curve. It's used in bitcoin and many other crypto currencies.
Bitcoin deployment now numbers in the millions of users and hundreds of
companies. There are also free software implementations in most
languages.
For more background on Koblitz curve used by bitcoin see:
https://bitcointalk.org/?topic=2699.0
I'm aware that the API tends to expose what's existing in NSS, but, imho,
if it were possible to add support for this curve would be a great step to
help to many people that already work with crypto currencies in the browser.
--089e013c68e27e64e304ed969a89
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Harry and David suggested I send a message to this gr=
oup.=A0 I was wondering if the crypto group may consider adding support for=
<b>secp256k1</b>
in the browser Named Curve dictionary.=A0 <br><br></div><a href=3D"http://=
www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dictionary" target=3D"_blank">ht=
tp://www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dictionary</a><br>
<br>enum NamedCurve {<br>=A0 // NIST recommended curve P-256, also known as=
secp256r1.<br>=A0 "P-256",<br>=A0 // NIST recommended curve P-38=
4, also known as secp384r1.<br>=A0 "P-384",<br>
=A0 // NIST recommended curve P-521, also known as secp521r1.<br>=A0 "=
P-521"<br>};<br><br>Over the last year, there has been a significant i=
ncrease in deployment for this curve.=A0 It's used in bitcoin and many =
other crypto currencies.=A0 Bitcoin deployment now numbers in the millions =
of users and hundreds of companies.=A0 There are also free software impleme=
ntations in most languages.=A0 <br>
<div><div><div><div><div><div><br></div>For more background on <span>Koblit=
z</span> curve used by bitcoin see:<br>
<br><a href=3D"https://bitcointalk.org/?topic=3D2699.0" target=3D"_blank">h=
ttps://bitcointalk.org/?topic=3D2699.0</a><br><br></div>I'm aware that =
the API tends to expose what's existing in NSS, but, imho, if it were p=
ossible to add support for this curve would be a great step to help to many=
people that already work with crypto currencies in the browser.</div>
</div></div></div></div>
--089e013c68e27e64e304ed969a89--
|
