3 ms·
When DJB has already designed CurveCP et al, why would we use this? Presumably he got the usage of his own crypto primitives right.
by revelation 12y ago
When DJB has already designed CurveCP et al, why would we use this? Presumably he got the usage of his own crypto primitives right.
- e1ven 12y agoThis is discussed at https://github.com/trevp/noise/wiki/Noise-properties-and-protocol-comparisons#pipe-like-protocols https://github.com/trevp/noise/wiki/Noise-properties-and-pro... CurveCP: CurveCP lacks in-connection forward secrecy and resistance to key-compromise impersonation for the server. Also, a compromised ephemeral client key can be used permanently for impersonating the client. CurveCP requires the client to know the server's key prior to connecting, so trust models based on server certificates or "Trust-on-First-Use" are not directly supported. Like NaCl, it has a 128-bit security level.