Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Random Connection Issue with Cisco Kit #778

Closed
darkoperator opened this issue Feb 4, 2021 · 2 comments
Closed

Random Connection Issue with Cisco Kit #778

darkoperator opened this issue Feb 4, 2021 · 2 comments
Milestone
2023.0.1

Comments

@darkoperator
Copy link

Since version 2020 the powershell module I wrote has been having issues with Cisco kit, it seems to get stuck in the kinit part as it selects the encryption to use darkoperator/Posh-SSH#376
@Sparin Sparin mentioned this issue Jun 24, 2021
Closed
likeMyCoffee added a commit to likeMyCoffee/SSH.NET that referenced this issue Jun 29, 2021
@likeMyCoffee
Cisco connection issue fix
bd95e41 
Certain Cisco devices do not adhere to RFC4342 and do not reply if the client identifies first.
Since identifcation can be in random order it will give random connection issues because the SSH_MSG_KEXINIT will not be sent if the client is faster.

Since SSH.Net is not at fault and compatibility with Cisco (and possibly other) devices is something that can easily be supported I've written this modification.

Added LazyIdentification to the ConnectionInfo object to allow late identification in ProtocolVersionExchange.
Overloaded 'Start' function to keep the original functionality and tests intact.

Highly likely fixes issues sshnet#752, sshnet#778, sshnet#469 and might help with sshnet#798, sshnet#767, sshnet#807
likeMyCoffee added a commit to likeMyCoffee/SSH.NET that referenced this issue Jun 29, 2021
@likeMyCoffee
Cisco connection issue fix
60069be 
Certain Cisco devices do not adhere to RFC4342 and do not reply if the client identifies first.
Since identifcation can be in random order it will give random connection issues because the SSH_MSG_KEXINIT will not be sent if the client is faster.

Since SSH.Net is not at fault and compatibility with Cisco (and possibly other) devices is something that can easily be supported I've written this modification.

Added LazyIdentification to the ConnectionInfo object to allow late identification in ProtocolVersionExchange.
Overloaded 'Start' function to keep the original functionality and tests intact.

Highly likely fixes issues sshnet#752, sshnet#778, sshnet#469 and might help with sshnet#798, sshnet#767, sshnet#807
@likeMyCoffee likeMyCoffee mentioned this issue Jun 29, 2021
Closed
@WojciechNagorski
Copy link
Collaborator

It's done in #1274

@WojciechNagorski WojciechNagorski added this to the 2023.0.1 milestone Dec 21, 2023
@WojciechNagorski
Copy link
Collaborator

The 2023.0.1 version has been released to Nuget: https://www.nuget.org/packages/SSH.NET/2023.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2023.0.1
Development

No branches or pull requests
2 participants
@darkoperator @WojciechNagorski