Describe the solution you'd like
Create a new option to use a local file for the key such as with privateKeyPathLocal.
Describe alternatives you've considered
If a same remote hop user is used among several users, the same remote hop user must hold everyone's actual target servers' private key, so the hop user also must be separated and created on the hop server. Private keys should really stay with the user.
Is this a similar or duplicate feature request?
Is your feature request related to a problem? Please describe.
The remote key file uses a file on the hop server instead of on the local machine like OpenSSH handles using
ProxyCommand
.This issue was submitted in the previous repo here. https://github.com/liximomo/vscode-sftp/issues/756
Describe the solution you'd like Create a new option to use a local file for the key such as with
privateKeyPathLocal
.Describe alternatives you've considered If a same remote hop user is used among several users, the same remote hop user must hold everyone's actual target servers' private key, so the hop user also must be separated and created on the hop server. Private keys should really stay with the user.
Does this project help you?