Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use OpenSSH in backend / SSH Agent Support #278

Open
Awbmilne opened this issue Oct 29, 2020 · 2 comments
Open

Use OpenSSH in backend / SSH Agent Support #278

Awbmilne opened this issue Oct 29, 2020 · 2 comments

Comments

@Awbmilne
Copy link

Environment

  • Extension version: 0.5.2
  • OS Type: Windows

Summary

This extension seems to require an actual private key to be present. This means that using an agent for key management is not supported. Couldnt the extension just utilize OpenSSH of OS to make the connection? This would eliminate the need for a custom servers.json file.

The ~/.ssh/config file already has the options available and is well established. It great for users of SSH for servers they interact with. This would also allow OpenSSH to handle key and password gathering. So I could use my Yubikey and GPG-agent for the SSH authentication

(Refer to benpye/wsl-ssh-pageant for gpg-agent integration with Windows OpenSSH, refer to drduh/YubiKey-Guide for Yubikey GPG guide)

Reproduce steps

Try using with agent

Expected Results

It uses standard SSH to connect and run commands (maybe using Agent-Forward if needed)

Actual Results

It asks for path to a private key (Which doesnt exist on my computer, for security reasones).
I am sad because it I have hit a road-block.

@Gr4cchus
Copy link

Gr4cchus commented Dec 17, 2020

Is this still unresolved? Also having issues figuring out how to use the yubikey with this extension. For the ssh fs extension theres an option in the configuration to specify the environment variable that solves the problem of providing a key.
image

@Awbmilne
Copy link
Author

Awbmilne commented Dec 18, 2020

It seems this extension has been retired... 😢

#282

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants