Disposing connections in Event "client_ErrorOccurred"
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 993
- Avg merge
- 9d 21h
- Merged PRs (30d)
- 1
Description
Hello, i have one problem with the library. Everything is working fine, except when i want to handle the client_errorOccured event.
If i disconnect and dispose the connection in it, it seems to have no real effect. We have one firewall which RAM is running full due to the dead ssh connections staying somehow open.
I am using Version 2016.0.0 (cause we are stuck on .net 4.5 due to project requirement).
Is this behaviour known or anything i can do? Thank you in advance :)
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 by reproducing the reported behavior in SSH.NET 2016.0.0 on .NET 4.5, focusing on disconnecting and disposing the connection from the client_ErrorOccurred event. Trace the connection lifecycle and verify that the firewall no longer retains the SSH connection after the error is handled.
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
- 25/100