-
-
Notifications
You must be signed in to change notification settings - Fork 946
Add functionality to communicate with remote commands over stdin #1052
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
Conversation
* Create FUNDING.yml * Add sponsor info.
# Conflicts: # build/sandcastle/SSH.NET.shfbproj
@drieseng This is a really important issue for the entire .NET. We need this change for Docker.DotNet library that has 9.1M downloads. Currently, no one is able to create a real docker manager using .NET, because it can work only locally or with unsafe remote connections without encryption. Thanks to this PR the community will be able to communicate with Docker via the safe encrypted connection. Can you help with this PR? |
@drieseng Would you have any idea if you're going to be able to have a look at this PR, please? Your help would really be appreciated. Thank you |
@mdarocha Tests do not pass. Can you check it? |
Unfortunately I don't have the time to work on this PR anymore. I'm closing it, if anybody wants to pick up this work, feel free to do it. |
This issue has been fixed in the 2024.0.0 version. |
Fixed by #1293 |
This is a rebase and update of #144, with the sole purpose being adding functionality to communicate with commands executed over ssh using stdin.
This functionality is needed by ie. dotnet/Docker.DotNet#575
This PR reimplements functionality requested in #141, InputStream seems to have been lost in the original rewrite PR