Issue with forced ssh-agent link in NFS shared home

Bug #1893232 reported by Simon Sudler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
byobu
New
Undecided
Unassigned

Bug Description

Byobu always creates a link to an existing ssh-agent socket in the user home ~/.byobu/.ssh-agent.

While this is convenient to have always the same name for the socket, this fail terribly on home that are shared via NFS server (or any other way like sshfs).
As I quick fix I would recommend to replace the link from:

# Drop a symlink to the ssh socket in $HOME, since we can ensure that exists
if [ -S "$SSH_AUTH_SOCK" ] && [ ! -h "$SSH_AUTH_SOCK" ]; then
        ln -sf "$SSH_AUTH_SOCK" "$BYOBU_CONFIG_DIR/.ssh-agent"
        export SSH_AUTH_SOCK="$BYOBU_CONFIG_DIR/.ssh-agent"
fi

with a simple

# Drop a symlink to the ssh socket in $HOME, since we can ensure that exists
if [ -S "$SSH_AUTH_SOCK" ] && [ ! -h "$SSH_AUTH_SOCK" ]; then
        ln -sf "$SSH_AUTH_SOCK" "$BYOBU_CONFIG_DIR/.ssh-agent-$(hostname)"
        export SSH_AUTH_SOCK="$BYOBU_CONFIG_DIR/.ssh-agent-$(hostname)"
fi

to avoid that. But this would invalidate the always the same name for the agent socket. Any suggestions on howto avoid this

Tags: ssh-agent
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.