-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Allow forwarding of SSH & GPG agents in VSCode extension. #6993
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
Comments
there is a discussion about similar thing here #666 hope that helps |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is related to: #666 |
(Posting this here, because the other issue is more about GPG in general) Here's what I'm running into when SSH'ing into a Gitpod workspace with agent forwarding enabled:
Is this a bug, known issue, something on my end? Or just unsupported as of now? |
@iQQBot since I think you worked on SSH agent, can you provide some answers to above? |
SSH Gateway is support ssh-agent-forward (wait this PR deploy) @florisvdg |
@florisvdg SSH Gateway is support ssh-agent-forward now, PR is deployed |
For newcomers to this issue, I just want to add that this solution does not work in the browser |
Is your feature request related to a problem? Please describe
When using the VSCode extension to connect to my workspace, I would like to have my SSH and GPG agents forwarded so that I have access to my signing keys for commits and SSH keys for accessing resources.
Describe the behaviour you'd like
The extension should offer some commands to enable the forwarding of the agents.
Describe alternatives you've considered
This is possible in the stock VSCode Remote SSH extension, which relies on the user's SSH configuration file. My only alternative is to create a GPG subkey and then have this provided as a variable through GitPod, but this is cumbersome and messy when I have a YubiKey attached to my machine ready to be accessed.
The text was updated successfully, but these errors were encountered: