-
-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for ecdh-sha2-nistp256 #210
Comments
:( Duplicate of #201 |
Yeah but not ecdh-sha2-nistp256 |
🤦 |
+1 on the request for support for the @Eugeny, I noticed a comment in curve25519.rs about NIST P-256 formerly being supported. According to blame, this looks like something forked from thrussh (thrussh's source repo won't load for me at the moment, so hard to confirm). Would it be possible to add back in this implementation? And if there are concerns over the security of the kex, maybe leave these three off of the default preferred safe kex order but still allow a client to opt-in with a custom config? |
@gleason-m yes, that's inherited from I don't have a lot of time to work in |
Adds support for ecdh-sha2-nistp{256,384,521} key exchange algorithms using the [elliptic-curve](https://docs.rs/elliptic-curve/latest/elliptic_curve/index.html), [p256](https://docs.rs/p256/latest/p256/index.html), [p384](https://docs.rs/p384/latest/p384/), and [p521](https://docs.rs/p521/latest/p521/) crates. Intentionally avoids adding these to the preferred Kex list as the security of these curves is considered controversial. Users would need to explicitly use the kex via config Resolves #210 --------- Co-authored-by: Eugene <inbox@null.page>
Would be nice if support added for "ecdh-sha2-nistp256"
The text was updated successfully, but these errors were encountered: