client side ssh agent support instead of path to key file
Posted: Fri Oct 06, 2023 1:33 am
Hi,
Is implementing ssh agent support for vms ide on the roadmap ? I'm guessing it's not currently supported based on https://wiki.vmssoftware.com/SSH_Settings
https://github.com/mscdex/ssh2#readme e.g has agent in it's connect call
but i'm not sure about ssh2-streams support for this. I am guessing as mentioned in passing before in the previous issue that you are using your own fork of ssh2-streams for the connection to VMS (https://github.com/vmssoftware/ssh2-streams), but it's unclear from my scan of their readme whether it has support
Ideally i'd be able to use vms ide using ssh-agent, like configured here https://learn.microsoft.com/en-us/windo ... generation OR failing that pageant.
Is implementing ssh agent support for vms ide on the roadmap ? I'm guessing it's not currently supported based on https://wiki.vmssoftware.com/SSH_Settings
https://github.com/mscdex/ssh2#readme e.g has agent in it's connect call
Code: Select all
agent - string - Path to ssh-agent's UNIX socket for ssh-agent-based user authentication. Windows users: set to 'pageant' for authenticating with Pageant or (actual) path to a cygwin "UNIX socket." Default: (none)
Ideally i'd be able to use vms ide using ssh-agent, like configured here https://learn.microsoft.com/en-us/windo ... generation OR failing that pageant.