From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Fwd: [Bug 24444] Named Curve Registry (adding secp256k1)
Date: Mon, 13 Oct 2014 12:01:37 +0200 [thread overview]
Message-ID: <CAKaEYhJPFoaSzPuGH80u3y6XoYCOpeQ0=3qote3jdwNVegoiVQ@mail.gmail.com> (raw)
In-Reply-To: <bug-24444-7046-xvP1kb2tHS@http.www.w3.org/Bugs/Public/>
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
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>
Date: 13 October 2014 09:18
Subject: [Bug 24444] Named Curve Registry (adding secp256k1)
To: melvincarvalho@gmail•com
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24444
Myron Davis <myrond@gmail•com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |myrond@gmail•com
Resolution|NEEDSINFO |---
--- Comment #2 from Myron Davis <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.
[-- Attachment #2: Type: text/html, Size: 2930 bytes --]
next parent reply other threads:[~2014-10-13 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-24444-7046@http.www.w3.org/Bugs/Public/>
[not found] ` <bug-24444-7046-xvP1kb2tHS@http.www.w3.org/Bugs/Public/>
2014-10-13 10:01 ` Melvin Carvalho [this message]
2014-10-13 17:18 ` Matt Corallo
2014-10-14 8:57 ` Melvin Carvalho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKaEYhJPFoaSzPuGH80u3y6XoYCOpeQ0=3qote3jdwNVegoiVQ@mail.gmail.com' \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox