W3C home > Mailing lists > Public > public-webcrypto@w3.org > July 2014

[Bug 25839] Curve25519 Named Curve

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Jul 2014 16:29:17 +0000
To: public-webcrypto@w3.org
Message-ID: <bug-25839-7213-diTHIPLo3n@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839

webcrypto@trevp.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |webcrypto@trevp.net

--- Comment #44 from webcrypto@trevp.net ---

Hi,

Has this issue reached resolution?

I know that TextSecure (which Matt Corallo and I work on) uses Curve25519, and
many other projects are either using it (SSH [1], Tor [2], CryptoCat [3],
miniLock [4]); or have expressed interest (PGP [5], OTR [6], TLS [7]).

I suspect Javascript will not be used much for older network-layer protocols
like IPsec, where NIST curves have found favor.  Rather, Javascript will be
used for newer protocols where people are choosing Curve25519 due to its better
performance.

It would be unfortunate if this API omits the curve that most new projects are
choosing.

[1]
http://git.libssh.org/projects/libssh.git/tree/doc/curve25519-sha256@libssh.org.txt
[2]
https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=tor-spec.txt
[3]
https://github.com/cryptocat/cryptocat/wiki/Multiparty-Protocol-Specification
[4] http://minilock.io/
[5] https://moderncrypto.org/mail-archive/curves/2014/000195.html
[6] https://lists.cypherpunks.ca/pipermail/otr-dev/2014-July/002183.html
[7] https://datatracker.ietf.org/doc/draft-josefsson-tls-curve25519/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 23 July 2014 16:29:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:23 UTC