blob: f275173e17da1281cc38300fb2ecca089f25562a (
plain)
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
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
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 <bitcoin-list@bluematt.me>) 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 <bitcoin-development@lists.sourceforge.net>;
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 <bitcoin-list@bluematt.me>
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: <bug-24444-7046@http.www.w3.org/Bugs/Public/> <bug-24444-7046-xvP1kb2tHS@http.www.w3.org/Bugs/Public/>
<CAKaEYhJPFoaSzPuGH80u3y6XoYCOpeQ0=3qote3jdwNVegoiVQ@mail.gmail.com>
In-Reply-To: <CAKaEYhJPFoaSzPuGH80u3y6XoYCOpeQ0=3qote3jdwNVegoiVQ@mail.gmail.com>
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: <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: 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: ** <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
>
|
