openssh bugs - Jul 2019 - [Bug 3034] New: provide options to map additional FDs

https://bugzilla.mindrot.org/show_bug.cgi?id=3034

            Bug ID: 3034
           Summary: provide options to map additional FDs
           Product: Portable OpenSSH
           Version: 8.0p1
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: brian at interlinx.bc.ca

While it's really cool that ssh will map the remote's std{in,out,err}
to the local FDs representing those streams, it would be nice to be
able to map additional remote FDs to local FDs.

A working example of how this might be useful:

#!/bin/bash

exec 3>/tmp/remote_xtrace
ssh --map_fd 3:3 remote "export BASH_XTRACEFD=3; id; ls -l"

That way one can get the xtrace of the remote script being run without
it polluting the stderr stream.

I am sure there are tons of other examples of how this would be useful.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3034

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |djm at mindrot.org

--- Comment #1 from Damien Miller <djm at mindrot.org> ---
This would need some pretty serious protocol extensions unfortunately.
The assumption that channels have at most an input, an output and a
stderr is heavily baked in to
https://datatracker.ietf.org/doc/html/rfc4254

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3034

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |LATER
             Status|NEW                         |RESOLVED

--- Comment #2 from Damien Miller <djm at mindrot.org> ---
This would probably need a major revision to the SSH protocol. This
might happen one day, but not likely any time soon

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.