Closed eugenov closed 3 years ago
mc is based on libssh2, whereas the window implementation is PowerShell/openssh-portable, direct integration is not feasible. Use of the OpenSSH ssh-agent may be a possible solution, which from initial research shall utilize the local certstore.
On further investigation to my surprise Win-OpenSSH seems to use local registry entries. I can not find any CertStore interaction within either the client nor the agent. Regardless the Win-OpenSSH agent uses a named pipe for ipc, libssh2 would need enhancing to support (libssh2/src/agent.c)
PuTTY's Pageantis is already supported by libssh2, suggest this the most suitable solution at this time.
libssh2 OpenSSH support is in the pipeline, https://github.com/libssh2/libssh2/pull/517
Since libssh2 will grab ~.ssh\config, for user it will be no difference: openssh or libssh2 somewhere inside, imao
Hello! Do you have any roadmap? TY!
Waiting on the next libssh2 release.
[libssh2] Update to 1.10.0 microsoft/vcpkg#20364
libssh2-1.10, target build-221
Is there any plans to migrate to libssh? It offers more openssh compatibility, and maintained by RedHat, as far as i know. In fact, now everithing works pretty well, just curious
@eugenov: @adamyg has done a new version, can you look?
@Neustradamus Just checked - mc respects ~.ssh\config file. It also works with Openssh agent. Perfect
But only for FISH, SFTP not supported
SFTP utilizes libssh2.
@adamyg and FISH - Openssh? Didn't get it. libssh2 bundled with mc, right? Openssh does not. Why FISH works but SFTP does not?
vfs/sftp connections are via libssh2, whereas Files transferred over Shell protocol (FISH) over SSH, an ssh client is required, you can either install Win32-OpenSSH or WinXSH. For legacy RSH based connections WinXSH is needed.
Hello! Is there any way to integrate mc with windows 10 built-in Openssh? SFTP feature is not so usable at moment, but with ~/.ssh/config reading will open all the doors: public key auth, jumphosts, etc.