-
Notifications
You must be signed in to change notification settings - Fork 427
Closed
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalityon-testplansshIssue in vscode-remote SSHIssue in vscode-remote SSH
Milestone
Description
- VSCode Version: Version 1.34.0-insider (1.34.0-insider)
- Local OS Version: Mac OS X Mojave 10.14.4 (18E226)
- Remote OS Version: Ubuntu Linux 18.04
- Remote Extension/Connection Type: SSH
Steps to Reproduce:
- Open remote folder/project workspace with git repository via SSH
- Try to commit something to an even more remote repo (say GitHub) that relies on SSH auth.
Since the remote server does not have your SSH key and the VS Code connection does not use agent forwarding, key validation by the Git server (GitHub in this case) fails because the remote machine cannot talk to your local SSH agent and does not have valid keys.
This is a breaking issue for anyone who has to work via jump boxes.
Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: N/A
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalityon-testplansshIssue in vscode-remote SSHIssue in vscode-remote SSH