SSH Client session is terminated but no event is triggered
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 993
- Avg merge
- 9d 21h
- Merged PRs (30d)
- 1
Description
There is an issue where the session is closed and ErrorOccured will not be triggered.
We have inserted the logging to the library and attached here in the issue.
We found that at 2019-12-13 09:18:07.319, the client sent 'ChannelCloseMessage' to the server but after that from 2019-12-13 09:18:07.410 onwards, the client again sent a few 'ChannelDataMessage' to the server again.
Finally at 2019-12-13 09:18:07.521, the server replied 'DisconnectMessage' and the client closed the SSH session completely without returning any events.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached issue_nonexistent_channel.txt log and trace the SSH session handling around the ChannelCloseMessage, subsequent ChannelDataMessage messages, and final DisconnectMessage. The fix is complete when this termination path triggers the expected ErrorOccured event instead of closing silently; no source file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100