You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add a flag and env variable for the equivalent of IdentityAgent in SSH configs. These would be coder ssh --identity-agent /path/to/auth.sock and CODER_SSH_IDENTITY_AGENT=/path/to/auth.sock. There is no shorthand flag for this in SSH, so I don't think we need one here.
Why do you want this feature?
This is a useful feature for users or organizations using multiple SSH identity agents and avoids situations where the user needs to work around the limitation by changing the SSH_AUTH_SOCK env variable.
Are there any workarounds to get this functionality today?
There are two:
Use SSH and change config, e.g. coder config-ssh -o 'ForwardAgent=yes' -o 'IdentityAgent "~/my/agent.sock"'
Modify the SSH_AUTH_SOCK env variable
Are you interested in submitting a PR for this?
Yes.
The text was updated successfully, but these errors were encountered:
What is your suggestion?
We should add a flag and env variable for the equivalent of
IdentityAgent
in SSH configs. These would becoder ssh --identity-agent /path/to/auth.sock
andCODER_SSH_IDENTITY_AGENT=/path/to/auth.sock
. There is no shorthand flag for this in SSH, so I don't think we need one here.Why do you want this feature?
This is a useful feature for users or organizations using multiple SSH identity agents and avoids situations where the user needs to work around the limitation by changing the
SSH_AUTH_SOCK
env variable.Are there any workarounds to get this functionality today?
There are two:
coder config-ssh -o 'ForwardAgent=yes' -o 'IdentityAgent "~/my/agent.sock"'
SSH_AUTH_SOCK
env variableAre you interested in submitting a PR for this?
Yes.
The text was updated successfully, but these errors were encountered: