[Bug 99065] Re: feature request: reviving ssh-agent

jtolds jtolds at xnet5.com
Thu Aug 2 00:12:44 UTC 2012


this is back for me in precise.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/99065

Title:
  feature request: reviving ssh-agent

Status in “openssh” package in Ubuntu:
  Expired

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/99065/+subscriptions




More information about the foundations-bugs mailing list