[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
** 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 subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
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 this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
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 4089 0.0 0.0 35936 688 ?Ss 10:04 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --e -- - mdz -- [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 subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
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/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 subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
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 subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
*** 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-keyring-daemon returns Agent admitted failure to sign using the key. -- [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 subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
** 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
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 4089 0.0 0.0 35936 688 ?Ss 10:04 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --e -- - mdz -- [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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
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 title of the bug. I get the same issue with programs: ssh, scp, rsync, putty. Like Matt, I'm running ssh-agent. :-Dustin :-Dustin ** Changed in: openssh (Ubuntu) Importance: Undecided = High Status: Incomplete = Confirmed -- [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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
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/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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
*** 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/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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328445] Re: [Jaunty/amd64] Agent admitted failure to sign using the key.
*** 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-keyring-daemon returns Agent admitted failure to sign using the key. -- [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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
