-
-
Notifications
You must be signed in to change notification settings - Fork 939
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
2024.1.0 version problem #1517
Comments
Strange, there were no algorithms removed between 2024.0.0 and 2024.1.0. There were aes-gcm ciphers added, and also the strict-kex extension I do see this kb but they don't provide any information about the algorithms that the server offers. Could you see what algorithms the server is offering? You can do that with nmap:
Or you might be able to inspect these properties on the client.ConnectionInfo.CurrentKeyExchangeAlgorithm
client.ConnectionInfo.CurrentServerEncryption
client.ConnectionInfo.CurrentServerHmacAlgorithm
client.ConnectionInfo.CurrentHostKeyAlgorithm
client.ConnectionInfo.CurrentServerCompressionAlgorithm You can also try this before connecting to rule out aes-gcm: client.ConnectionInfo.Encryptions.Remove("aes128-gcm@openssh.com");
client.ConnectionInfo.Encryptions.Remove("aes256-gcm@openssh.com"); |
And I also added following line before connection:
And the connection was successfully established with 2024.1.0 version. But I'm not sure if this still counts as a bug. Thank you |
Glad you got it working. It sounds like a bug but hard to tell whose side it is on For posterity, was it only the |
I have this exact same issue. If I removed all the encryption methods besides the Its almost like whatever code is used to determine the encryptions is not finding the correct one. This is from their knowledge base. They appear to prefer the gcm methods. Is there a way to have it "prefer" a specific encryption method? Is that just the order in the list? |
Interesting that they claim it is an issue with WinSCP/PuTTY. Seems to me that their server is not respecting the client algorithm priorities. cc @martinprikryl
It should be the order in the list that the client specifies. Currently SSH.NET is not entirely reliable in that regard because it uses Dictionary<> under the hood |
I'm facing same issue. My code was working fine till 15th Nov but not sure why I'm getting this error now. Can anyone please help me in this. I'm getting below error: I have tried with adding below 3 lines before establishing connection. sftpClient.ConnectionInfo.Encryptions.Remove("aes128-gcm@openssh.com"); |
@ravi-kamboj try removing all the keys EXCEPT the aes-gcm ones. Something like :
|
Yeah, that's kinda what I figured, no other SFTP host I've run into has this issue. For now, I just had to build a special exception when connecting to this host. |
When I try to connect with Ssh.net 2024.1.0 to Globalscape Eft 8.2.1.30, get following error:
But, with 2024.0.0 version, there is no problem. I supposed there's a MAC algorithm problem.
The text was updated successfully, but these errors were encountered: