4 ms·
Re: curve25519, just do what vendors always do: add it to your implementation as a proprietary extension and wait for everyone to adopt it as de facto standard.
by peterwwillis 12y ago
Re: curve25519, just do what vendors always do: add it to your implementation as a proprietary extension and wait for everyone to adopt it as de facto standard.
- tptacek 12y agoThe problem is Apple and Microsoft. If Curve25519 isn't standardized, Google and Firefox will implement it, and Unix servers will get support through OpenSSL, and so a big chunk of the web will get to use Curve25519, which is a bit of a win. However, Apple probably won't support Curve25519 without a standard, and Microsoft definitely won't: they have a competing proposal. Which will leave the NIST curves widely used across the web as well, because IE and Safari support is critically important.
- tedunangst 12y agore: Apple, that may be true for browsers, but they're already using it in other, not publicly exposed ways such as some of iOS file encryption.
- peterwwillis 12y agoHow are they a problem? Firefox/Chrome/OpenSSL can still pick up Curve25519, and Microsoft can still hold out for their own proposal; neither cancels the other out and we're already stuck with NIST curves (rfc4492). In fact, TLS specifically advertises what curves are available so that an upgraded server/client can use stronger curves in the future - optionally. I know MS will be dicks and try to force their own version of everything, but i'll bet Apple will implement anything that there's a half-decent reference implementation of. That just leaves Microsoft, and the easiest way to defeat their proposal is to get their customers to demand they support the thing everyone else already implements, which would be Curve25519.
- higherpurpose 12y agoDJB said in his recent talk that Microsoft is going to adopt "26 new curves", and he seemed pretty happy about it. But I'm not sure whether that means Microsoft will support Curve25519 or not. If they will indeed support 26 new curves, but they won't support Curve25519, that would be pretty silly of them.
- tptacek 12y agoYou missed some subtext. Read Bernstein's posts on CFRG to see his take on the MSFT proposal.
- sarciszewski 12y agoLet's imagine a scenario that could result from this: 1. DJB criticizes NIST and other standardization institutes and their curve selection choices 2. CFRG fails to recommend a curve (or a suite of curves) for TLS WG 3. Microsoft refuses to adopt Curve25519 4. Everyone else does 5. Interop problems 6. ????? 7. Everyone who has to clean up after this is aligned strongly towards standardization processes. That's how they are a problem. (For the record: This isn't a conspiracy theory, I don't think anyone wants this to happen and is actively trying to manipulate things to make it happen, it's merely a hypothesis on what could happen.)
- alextgordon 12y agoApple already uses Curve25519 for iOS encryption, so it's not like they're a stranger to it: https://www.apple.com/br/ipad/business/docs/iOS_Security_Oct12.pdf https://www.apple.com/br/ipad/business/docs/iOS_Security_Oct...