-
-
Notifications
You must be signed in to change notification settings - Fork 942
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
Allow writing to stdin of SshCommand #141
Comments
PR #144 now implements this. |
Could you, please, provide a high level view of how this will be used? |
There's the other PR that is more alive than this one (for stdout/stderr). The general idea is that you use streams to communicate with a remote process like you would on the local machine like with System.Diagnostics.Process with the stream properties StanardInput/StandardOutput/StandardError. |
It's quite embarrassing that SSH.NET doesn't redirect stdin for remotely executed command. |
I have a fork that implements this feature. Shall I submit a PR for it? I'm asking because I think that there are already 2 dead PRs about this subject: #144 and #1052 . |
You should definitely create a new pull request. Previous pull requests do not pass unit and integration tests. This change is really important for me so if you create a pull request it will be on the first place on my list. |
@WojciechNagorski Please check out this PR: #1293 |
@WojciechNagorski Thanks for merging the PR! |
Fixed by #1293 |
SshCommand doesn't currently implement any way to write a long binary stream into stdin of the executed process.
SshCommand would need an
InputStream
property that would provide a writable stream which would also send the EOF packet when closed by the writer.The text was updated successfully, but these errors were encountered: