Skip to content
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

Agent forwarding handling by tsh #1571

russjones opened this issue Jan 10, 2018 · 1 comment

Agent forwarding handling by tsh #1571

russjones opened this issue Jan 10, 2018 · 1 comment


Copy link

@russjones russjones commented Jan 10, 2018


Starting with Teleport 2.4.0 -A was added to tsh to allow forwarding the running agent to the target node. For tsh this is a agent that is created in-memory with keys from ~/.tsh this means it non-Teleport certificates and keys will not be forwarded using tsh -A.

Note: To work around this issue for now, ssh can be used to connect to a node within the Teleport cluster and whatever agent that can be reached at $SSH_AUTH_SOCK will be used.

@kontsevoy kontsevoy self-assigned this Jan 10, 2018
@kontsevoy kontsevoy added this to the 2.5.0 "New York" milestone Jan 10, 2018
@klizhentas klizhentas modified the milestones: 2.5.0 "New York", 2.5.1 "Portland" Feb 19, 2018
@kontsevoy kontsevoy removed this from the 2.5.3 "Portland" milestone Mar 19, 2018
@benarent benarent added the tsh label Aug 6, 2019

This comment has been minimized.

Copy link

@soedar soedar commented Feb 13, 2020

I'd love to see this feature implemented, as it appears that tsh ssh is intended to be used as a drop in replacement to be a somewhat drop in replacement for ssh.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
You can’t perform that action at this time.