** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22546945/Dependencies.txt
--
[Jaunty/amd64] Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328445
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Which agent, exactly? ssh-agent, gpg-agent (which under some
circumstances also provides an SSH agent) or seahorse?
** Changed in: openssh (Ubuntu)
Status: New = Incomplete
--
[Jaunty/amd64] Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328445
You received
On Thu, Feb 12, 2009 at 10:57:28AM -, Soren Hansen wrote:
Which agent, exactly? ssh-agent, gpg-agent (which under some
circumstances also provides an SSH agent) or seahorse?
perseus:[~] ps u $SSH_AGENT_PID
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
mdz
Downgrading to openssh-client_5.1p1-3ubuntu1_amd64.deb solves the
problem for me.
Looking at the changelog, I see that openssh-blacklist and openssh-
blacklist-extra were dropped to suggests, and are not currently
installed on my system. Perhaps this is causing the problem?
:-Dustin
--
Tried installing openssh-blacklist and openssh-blacklist-extra; does
not solve the problem.
:-Dustin
--
[Jaunty/amd64] Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328445
You received this bug notification because you are a member of Ubuntu
Server Team, which
*** This bug is a duplicate of bug 328127 ***
https://bugs.launchpad.net/bugs/328127
Actually, I can set SSH_AUTH_SOCK to anything (adsfasdfasdfasdf), or
unset it.
I'm going to mark this bug a duplicate of Bug #328127.
:-Dustin
** This bug has been marked a duplicate of bug 328127
