openssh bugs - Dec 2024 - [Bug 3762] New: ForkAfterAuthentication doesn't work with Windows native SSH

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

            Bug ID: 3762
           Summary: ForkAfterAuthentication doesn't work with Windows
                    native SSH
           Product: Portable OpenSSH
           Version: 9.5p1
          Hardware: Other
                OS: Windows 10
            Status: NEW
          Severity: normal
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: devstemail at gmail.com

When using Windows 10 or 11 native OpenSSH client,
ForkAfterAuthentication won't fork/send the ssh connection to the
background.

`ssh my-tunnel`

SSH config file:

```
Host my-tunnel
        User foo
        RemoteForward 9099 localhost:9003
        Hostname bar.com
        SessionType none
        RequestTTY no
        ServerAliveInterval 300
        ForkAfterAuthentication yes
        IdentitiesOnly yes
        PreferredAuthentications publickey
        PasswordAuthentication no
        IdentityFile C:\Some\Path\private.key
```

(same issue when using -f instead of ForkAfterAuthentication)

When using ssh that comes bundled with e.g. "Git for Windows", it
works
perfectly fine though.
I found that there was a fixed bug for Cygwin
https://bugzilla.mindrot.org/show_bug.cgi?id=1278 (via
https://superuser.com/questions/965374/setup-ssh-in-background-windows),
which I assume is what also fixed this for the ssh that comes with "Git
for Windows".
However for the native OpenSSH ssh client it's not working still.

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

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

devstemail at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P5                          |P2

--- Comment #1 from devstemail at gmail.com ---
Sorry if I reported this in the wrong place - just found
https://github.com/PowerShell/Win32-OpenSSH/issues/2209

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

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

Darren Tucker <dtucker at dtucker.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID
                 CC|                            |dtucker at dtucker.net

--- Comment #2 from Darren Tucker <dtucker at dtucker.net> ---
That's OK, thanks for following up.

Yes, the Windows fork is substantially different to the code we supply
so you need to talk to Microsoft for help, unless you can reproduce the
problem on the stock code from openssh.com.

(In fact the same goes for any vendor that modifies the code: if the
problem can't be reproduced on the stock code we can't help you.)

-- 
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.