Updates use of SSH_AUTH_SOCK var #1658
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On tmux terminals, the SSH_AUTH_SOCK points at a symlink. This change makes sure that the link is followed to the real file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On tmux terminals, the SSH_AUTH_SOCK points at a symlink and the function to create the ssh-agent file tries to incorrectly use the home directory.
This change makes sure that the link is followed to the real file by adding
readlink -finto flow each time the SSH_AUTH_SOCK variable is called.BEFORE
echo $SSH_AUTH_SOCK-->/home/[user]/.byobu/.ssh-agentAFTER
echo $(readlink -f $SSH_AUTH_SOCK)-->/tmp/ssh-hm7Kr86BHu/agent.1287