Uh oh!
There was an error while loading. Please reload this page.
Add functionality to communicate with remote commands over stdin - #1052
Add functionality to communicate with remote commands over stdin#1052mdarocha wants to merge 35 commits into
Conversation
* Create FUNDING.yml * Add sponsor info.
# Conflicts: # build/sandcastle/SSH.NET.shfbproj
WojciechNagorski
commented
Feb 21, 2023
@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? |
preetmyob
commented
Mar 31, 2023
@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 |
WojciechNagorski
commented
May 29, 2023
@mdarocha Tests do not pass. Can you check it? |
mdarocha
commented
Jan 25, 2024
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. |
WojciechNagorski
commented
Feb 22, 2024
This issue has been fixed in the 2024.0.0 version. |
WojciechNagorski
commented
Feb 22, 2024
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