openssh bugs - Jul 2024 - [Bug 3710] New: Use of ProxyCommand causes ssh session to never continue prompting for input

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

            Bug ID: 3710
           Summary: Use of ProxyCommand causes ssh session to never
                    continue prompting for input
           Product: Portable OpenSSH
           Version: 9.5p1
          Hardware: Other
                OS: Windows 11
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: phpfreaked9 at gmail.com

I am using a windows based version of openssh, and when I use proxy
command the command never prompts for user input.

In my scenario I wanted to use a simple script to automate some steps
everytime before establishing a connection to specific machine, so
according to what I could find the proxy command could be used for a
nesting the ssh command.

When I use this though, it seems that everything does connect
successfully however the stdout is being interpreted as banner and it
doesn't seem to recognize whatever it's considering as banner is
actually already the ssh session intended to be forward to the user.

The session is however stuck thinking it's reading banner, and the user
never gets prompted for input.

I've made a more extensive bug report here
https://github.com/PowerShell/Win32-OpenSSH/issues/2253

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

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

Lawrence <phpfreaked9 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |https://github.com/PowerShe
                   |                            |ll/Win32-OpenSSH/issues/225
                   |                            |3
                 CC|                            |phpfreaked9 at gmail.com

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

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

--- Comment #1 from Lawrence <phpfreaked9 at gmail.com> ---
Created attachment 3824
  --> https://bugzilla.mindrot.org/attachment.cgi?id=3824&action=edit
ssh session recorded in banner lines

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

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

Lawrence <phpfreaked9 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|enhancement                 |normal

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

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

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX
                 CC|                            |djm at mindrot.org

--- Comment #2 from Damien Miller <djm at mindrot.org> ---
Well, yes. ProxyCommands require stdin/stdout for SSH traffic only and
anything else that appears there is likely to break the connection. So
ProxyCommands should only ever output to stderr. This is not a bug,
it's the way ProxyCommands work.

Also, from the looks of what you're trying to do, you'd probably be
better off with a LocalCommand instead of ProxyCommand. LocalCommand is
not subject to the same restrictions.

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

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

--- Comment #3 from Lawrence <phpfreaked9 at gmail.com> ---
Sorry for the inconvience, I misinterpreted how proxy command worked
due to published examples referencing ssh direclty. To my understanding
LocalCommand isn't suitable to my needs, the whole point is, to
establish a tcp tunnel and LocalCommand runs after authentication and
connection according to documentation?

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