Forward local private SSH keys to Codespaces #63187
Replies: 4 comments 3 replies
-
Originally posted at microsoft/vscode-remote-release#8816 |
Beta Was this translation helpful? Give feedback.
-
@craiglpeters if you have a chance, could you check this out? Thanks! |
Beta Was this translation helpful? Give feedback.
-
Codespaces does not support SSH agent forwarding. We recommend that you do not tightly couple your local environment with the remote as this can be brittle. Instead, we recommend that you use Codespaces secrets to make your SSH keys available within your Codespaces so that you can use them with any client (SSH, VS Code, JetBrains, etc). |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
When I login into a Github codespace with vscode, I find that my SSH keys (which I have installed in my local agent) are not being forwarded to the Codespace. On the other hand, if I use vscode-remote to a server via the Remote-SSH extension, the keys are forwarded correctly.
Forwarding private SSH keys would be useful to be able to access dependencies hosted in private Github repos (among other things).
Why my SSH keys are not forwarded also to the Codespaces?
Beta Was this translation helpful? Give feedback.
All reactions