Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

janw

dma_k wrote:

How access to ssh-agent is organized by client in Windows10 OpenSSH implementation? Via native pipe e.g. \\.\pipe\openssh-ssh-agent (from issue#207)?


Yes, I would assume so from this and other posts on GitHubt.
dma_k

I vote for this feature as well. I doubt that PuTTY team will add support for another agent... there might be religious reasons why they have implemented their own.
KeeAgent plugin for KeePass is able to create Cygwin/MSYS sockets on Windows. Usually the path is exported via SSH_AUTH_SOCK environment variable. Would be nice to have a support for these sockets.

@janw: How access to ssh-agent is organized by client in Windows10 OpenSSH implementation? Via native pipe e.g. \\.\pipe\openssh-ssh-agent (from issue#207)?

martin

Re: Support OpenSSH ssh-agent

Thanks for your suggestion.
Please suggest this to PuTTY team (WinSCP is using an implementation of SSH protocol from PuTTY).
janw

Support OpenSSH ssh-agent

Hi,
Microsoft will soon start to offer OpenSSH client and server (https://github.com/PowerShell/Win32-OpenSSH) in Windows 10 and Windows Server 2019 as native applications. Currently, a Beta version is available as an optional Windows feature.

I think it would make sense for WinSCP to support the OpenSSH key agent (ssh-agent) as an alternative to PuTTY's pageant.

Cheers,
Jan