* [Bitcoin-development] WebCryto standard to support secp256r1 but not secp256k1
@ 2013-05-07 10:18 Melvin Carvalho
2013-05-29 12:14 ` Melvin Carvalho
0 siblings, 1 reply; 2+ messages in thread
From: Melvin Carvalho @ 2013-05-07 10:18 UTC (permalink / raw)
To: Bitcoin Dev
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 846 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bitcoin-development] WebCryto standard to support secp256r1 but not secp256k1
2013-05-07 10:18 [Bitcoin-development] WebCryto standard to support secp256r1 but not secp256k1 Melvin Carvalho
@ 2013-05-29 12:14 ` Melvin Carvalho
0 siblings, 0 replies; 2+ messages in thread
From: Melvin Carvalho @ 2013-05-29 12:14 UTC (permalink / raw)
To: Bitcoin Dev
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
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 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 ...
[-- Attachment #2: Type: text/html, Size: 2482 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-05-29 12:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-05-07 10:18 [Bitcoin-development] WebCryto standard to support secp256r1 but not secp256k1 Melvin Carvalho
2013-05-29 12:14 ` Melvin Carvalho
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox