[manu0401]

Windows native OpenSSH has alternative behavior for standard I/O descriptors, which can be selected through the OPENSSH_STDIO_MODE environement variable. Setting it to "nonsock" is required for sshfs compatibility.

See PowerShell/openssh-portable#759 for details.

Subitted upstream here
libfuse/sshfs#314

[manu0401]

I forgot to add this (along latest PowerShell/openssh-portable) will fix the infamous "read - ERROR from cb :87" that was reported at least in 6 PR:
https://github.com/winfsp/sshfs-win/issues?q=is%3Aissue+cb+%3A87

[billziss-gh]

This looks like a great solution to this problem. I am testing it now.

To clarify: this needs latest PowerShell/openssh-portable to work?

[billziss-gh]

I tried testing with the latest release of OpenSSH that I can find here: v9.8.1.0p1-Preview, but was not able to make it work.

Is your OpenSSH fix available somewhere for me to test?

EDIT: I see now that this has not been released yet as your OpenSSH commit was only added yesterday. Is this fix available somewhere or would I have to build OpenSSH from source?

[manu0401]

For now you need to build from sources, as there is not yet any released binary. The build process is documented here https://github.com/PowerShell/openssh-portable/blob/latestw_all/contrib/win32/openssh/README.txt and works fine

You need to download Visual Studio Code.

I can also you an x64 ssh.exe binary with the change built-in.

[billziss-gh]

I can confirm that SSHFS with your changes together with patched SSH from PowerShell/openssh-portable works.

Thank you for submitting the PRs here and in PowerShell/openssh-portable, which fix a long-standing problem. I will be merging this PR.

---

FYI, I was able to build the PowerShell/openssh-portable project, but I had a couple of issues which I am documenting here in case you are more involved with that project:

• The build failed on my first attempt, because vswhere.exe locates a copy of VS2019 instead of VS2022 on my machine. I was able to overcome this by adding -version 17 to the vswhere.exe command line in OpenSSHBuildHelper.psm1.

• The resulting ssh.exe did not run and exited with STATUS_ENTRYPOINT_NOT_FOUND and the message "the procedure entry point BN_set_flags could not be located". I was able to overcome this by copying file libcrypto.dll from contrib\win32\openssh\LibreSSL\bin\desktop\X64 to bin\x64\Release as suggested in Compiled OpenSSH 9.2.0.0 sshd can not be started due to entry point BN_set_flags could not be located PowerShell/Win32-OpenSSH#2052 (comment).

[manu0401]

Upstream pull request in libfuse/sshfs has been merged.