[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.

2009-02-12 Thread Dustin Kirkland
*** 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 gnome-

[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.

2009-02-12 Thread Dustin Kirkland
*** This bug is a duplicate of bug 328127 *** https://bugs.launchpad.net/bugs/328127 I note that when I'm having this problem: SSH_AUTH_SOCK=/tmp/keyring-9rqJvO/socket.ssh I can workaround (solve?) this problem by: export SSH_AUTH_SOCK=/tmp/ssh-ilNHaf4279/agent.4279 :-Dustin -- [Jaunty/am

[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.

2009-02-12 Thread Dustin Kirkland
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 is

[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.

2009-02-12 Thread Dustin Kirkland
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 -- [Jaunty/

[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.

2009-02-12 Thread Dustin Kirkland
Thanks for opening the new bug. I'm marking confirmed, and high. I found that I could create a new key, and happily use that new keypair for public key authentication until I rebooted. Once I reboot, it's almost like that key is "blacklisted", and no longer usable per the error message in the ti

Re: [Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.

2009-02-12 Thread Matt Zimmerman
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 4

[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.

2009-02-12 Thread Soren Hansen
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

[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.

2009-02-12 Thread Matt Zimmerman
** 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 su