Support for OpenSSH agent authentication ?

[aetonsi]

Hello
i've tried to connect to my ssh fs via a passphrase encrypted key file, as per #218 , but i've never been able to make it work. As also #218 (comment) explicitly asks, it would be useful if Sirikali could work using windows' OpenSSH, which is well integrated in the OS at this point.
This could simply mean using the ssh.exe binary located in C:\Windows\System32\OpenSSH or C:/Windows/Sysnative/OpenSSH (since it appears that the app is 32 bit so system32 is shadowed). I tried prepending both paths to the "executable paths" in sirikali's settings, but it didn't work.
An alternative would be to allow the use of OpenSSH's ssh-add.exe to return the key/keys to try: C:\Windows\System32\OpenSSH\ssh-add.exe -L returns every public key registered with the agent, one per line.

Could any of this be possible via the sshfs argument -o ssh_command=... ?
I see that there's already an "ExternalExecutable" key option that maybe can already be of help, but i don't understand how it works and i can't find any documentation.

Thank you for your time

[aetonsi]

Mmh i see from the winsfp/sshfs-win repo that agent support (openssh or others) has already been discussed there without any solution... i guess Sirikali depends entire on that repo, right?

[mhogomchungu]

SiriKali just sets "SSH_AUTH_SOCK" environmental variable and its up to sshfs-win to pick it up and use it so SiriKali/sshfs-win should work with any key agent that supports sending credentials to sshfs-win through a socket path.

The question is, does "ssh-add.exe" create a unix socket path for sshfs-win to use?

[aetonsi]

Mmh i sincerely don't know, but if you're referring to this PowerShell/Win32-OpenSSH#1761 , then no, i don't think so