Replies: 4 comments
|
Related: #611 It's different, but a similar problem from another angle. |
|
EDIT: Nevermind, only works on initial connection. Setting this option seems to fix this issue when ForwardAgent is enabled in you ssh config. [remote]
manage_ssh_config = false |
|
Would probably work if herdr maintained a symlink per herdr instance pointing to the session ssh socket and exported that symlink as the SSH_AUTH_SOCKET to sub-processes, then update the symlink whenever a new remote connection is made. Don't know how you would handle it if there is more than one concurrent connection... maybe only update the symlink if an argument explicitly forcing it is provided when making the connection. |
|
Yes, this would be useful. Having to maintain a separate connection or to detach just to git pull/push is... very counterproductive. |
Uh oh!
There was an error while loading. Please reload this page.
idea / problem
Connecting herdr to the remote server is not very useful to me without being able to use my local ssh-agent.
requested change
Would be nice to have an option to forward the ssh-agent the same as
ssh -A ...doeswhy you want this
seamless git/ssh authentication without having to copy keys to remote hosts.
All reactions