- From: <bugzilla@jessica.w3.org>
- Date: Sat, 24 May 2014 18:18:28 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839 --- Comment #9 from Greg Slepak <hi@okturtles.com> --- (In reply to Ryan Sleevi from comment #8) > Yes, there is more than technical discussion here (although Curve25519 > remains a highly charged technical discussion). The political issues are > very much applicable for User Agents, particularly those that need to be > available to users in a variety of countries and purposes. > > While you can disagree with these, they are real issues that User Agent > vendors have to deal with. Things like export controls and FIPS 140-2 remain > issues for UAs and UA vendors. > > Still, a reasonable path forward is to provide separate curves in a separate > specification, which can then look at adding things like Curve25519, > Poly1305, Salsa 20, or the BADA55 curves. Could you please explain what a separate specification would achieve? Would it result in support for Curve25519 in Chrome and Firefox? If not, then what's the point of a separate specification? That then leads to a fork in the road. Get it? Fork? I made a funny! ;P -- You are receiving this mail because: You are on the CC list for the bug.
Received on Saturday, 24 May 2014 18:18:29 UTC