Public bug reported:
Binary package hint: openssh-client
ssh-agent sometimes dies on me. this leaves the problem that any
existing clients of that agent, as well as any processes that were
forked prior to the death of the agent, will be unable to reach the
agent. this is quite a nuisance, since it makes starting ssh-agent from
pam (using libpam-ssh) less useful.
i can't just resolve this by starting a new ssh-agent, because it will
have a different authentication socket than what the prior processes
expect. (those processes locate the ssh-agent via the SSH_AUTH_SOCK
environment variable.)
it would be nice to have an option to ssh-agent to connect to the same
socket as the previous agent. fwiw, for now, i'm using this script to
emualte the behavior i'd like:
#!/bin/sh
set -o errexit
if [[ -z $SSH_AUTH_SOCK ]]; then
>&2 echo "can't revive agent: SSH_AUTH_SOCK not set"
exit 1
fi
SSH_AUTH_DIR=$(dirname $SSH_AUTH_SOCK)
if [ ! -d $SSH_AUTH_DIR ]; then mkdir $SSH_AUTH_DIR; fi
rm -f $SSH_AUTH_SOCK
chmod go-rwx $SSH_AUTH_DIR
ssh-agent -a $SSH_AUTH_SOCK
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
feature request: reviving ssh-agent
https://launchpad.net/bugs/99065
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
