Open nikhiljha opened 4 years ago
This should be a doc change (encouraging the use of curves created in an open environment), not a change to our server side config. Calling nist-p256 and others weak is kinda a misnomer. The site is based of this talk, and is more about the curves being tricky to implement in practice.
If I recall correctly, most of the concern with the NIST elliptic curve algorithms is not a known weakness with the algorithm itself, but with the suspicious choice of parameters. If you look at the elliptic curve equations selected for NIST’s P algorithms, the coefficients seem ... quite large. And suspiciously arbitrary. Curve25519 has small numbers (255, 19) with open justifications, and appears to lend implementations resistance against side-channel attacks, so it is preferred regardless.
I’d like to make clear that old algorithms aren’t any less secure simply by being old. RSA is decades older than any of these and we still trust it; we actually tend to trust older algorithms that haven’t been broken because nobody’s been able to break them for so long.
Right now the algorithms mentioned in the title are actively in use in the ssh config.
https://github.com/ocf/puppet/blob/4e37cbedd228d89bc2f32234dbb4fc54114faa9d/modules/ocf/manifests/auth.pp#L175
However, these algorithms have known weaknesses. This is a super low-prio/nitpick issue, but it'd still be nice to fix it.
Ideally the config would be something like...
... but because of compatibility that's difficult.