Git credentials and SSH agent not forwarded when connected through SSH

[chrmarti]

I have been doing some initial testing and things are mostly working for me. Really nice job on this. I have one issue with git credentials. When running a devcontainer locally it will pick up the git credentials from the local OS if a credentials manager is configured (https://code.visualstudio.com/docs/remote/containers#_using-a-credential-helper). That does not appear to be happening when opening the container from a remote SSH connection. @chrmarti, Any guidance on this?

Originally posted by @hansenms in #2994 (comment)

[chrmarti]

/fyi @felipecrs for the SSH agent forwarding.

[zweiter]

The same is happening for me when using Remote SSH into any Linux system. I need to set SSH_AUTH_SOCK as explained in the issue #2671 that has been closed last year.

[chrmarti]

@zweiter This is about the Remote-Containers extension. Could you open a new issue for the problem with Remote-SSH?

[felipecrs]

Hey @chrmarti, I think you hit "Close" by mistake.

[hansenms]

I have an update on this. I have been experimenting some more and I have managed to somehow get git credentials to pass through. For one project I was testing it wasn't working and for another one it mysteriously appears to be working. I can't figure out the mechanics of it, but here is what I see:

I had an initial repo I was working on and to get things working, I installed the git credentials manager insider the devcontainer and that worked. Then I started a new repo and with its own devcontainer, that one seems to have picked up the settings from the other one....inside the second container, I get:

$ git config --global --list
credential.helper=!f() { /home/vscode/.vscode-server-insiders/bin/827f76521d33a61c19e92160649a0a6af8bad132-insider/node /tmp/vscode-remote-containers-e32ee6de56cec72419439a022d313eca32535d00.js $*; }; f
credential.credentialstore=cache
credential.cacheoptions=--timeout 86400
credential.https://dev.azure.com.usehttppath=true
user.name=XXXX
[email protected]

I am (almost) 100% sure I did not install anything in the second devcontainer to support this.

[chrmarti]

It will use the SSH server's Git credential helper if there is one. I have a fix ready that will make it consult localhost's credential helper if the one on the SSH server fails.

Similarly for the ssh-agent, if the SSH server does not have SSH_AUTH_SOCK set, the fix will check for it on localhost.

[interpeix]

I'm in the same situation.
My laptop (Windows machine with Git installed and GCM) and GCM is not forwarded to Remote-SSH Host.

Scenario 1:
My Laptop => Remote-SSH to linux host, trying to clone a repo that have the credentials saved on the windows machine fails.
$ git config --get credential.helper empty reply

Scenario 2:
Manually upload the content of the repository to the SSH Host, because there is a .devcontainer that I want to run.
My Laptop => Remote-SSH to linux host => Reopen folder remote container works without issues.
$ git config --get credential.helper Returns
!f() { /root/.vscode-server/bin/899d46d82c4c95423fb7e10e68eba52050e30ba3/node /tmp/vscode-remote-containers-673b0b90a3ad4447008f875661559991d7fdb747.js $*; }; f

Is there any workaround to be able to forward de GCM to the Remote-SSH host?

[chrmarti]

Created #6168 for @interpeix 's request.