-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Curve25519 kex panic #16
Comments
This is extremely strange since it looks like it's trying to use curve25519 KEX even though DH-group14-sha1 was negotiated. I'll release the latest code state as a new beta just in case. |
Published as |
|
Thanks. Could you please also post a full traceback with |
This may not be convenient for public access, but the https://mirror.dropbear.nl/mirror/releases/dropbear-2014.63.tar.bz2
|
Are you using any specific dropbear configuration? I couldn't reproduce it with |
no special configuration
|
I got a different problem after trying to modify it like this ( --- a/russh/src/negotiation.rs
+++ b/russh/src/negotiation.rs
@@ -80,7 +80,12 @@ impl Preferred {
#[cfg(feature = "openssl")]
pub const DEFAULT: Preferred = Preferred {
kex: KEX_ORDER,
- key: &[key::ED25519, key::RSA_SHA2_256, key::RSA_SHA2_512],
+ key: &[
+ key::ED25519,
+ key::RSA_SHA2_256,
+ key::RSA_SHA2_512,
+ key::SSH_RSA,
+ ],
Is there anything I can do to help with further testing? |
I also have such issue when I connect to a host like this:
Not sure if this is a host or client issue, and I'll be sharing more info if I could. |
I noticed
After some more digging, I found this line might be the cause to failed authentication: If I change the hash algorithm to the only supported #[cfg(feature = "openssl")]
fn decode_rsa(secret: &[u8]) -> Result<key::KeyPair, Error> {
Ok(key::KeyPair::RSA {
key: Rsa::private_key_from_der(secret)?,
hash: key::SignatureHash::SHA1,
})
} I think the |
I replied below this issue, but since the issue has been closed,I am worried that no one will see it, so I opened this issue.
The text was updated successfully, but these errors were encountered: