[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Hi again, Searching some informations on seahorse' ssh-agent, I found this thing: """/!\ Note: This only applies to versions of Seahorse prior to 2.22. In 2.22 and later a full SSH agent is included in gnome-keyring and the agent proxy in Seahorse has been retired. """ maybe there are some problems with versions of those programmes in ubuntu? See source: http://live.gnome.org/Seahorse/SSHAgent Regards, C. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Still present in Jaunty. Using SSH_AUTH_SOCK=0 still works around it. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I also had this problem in karmic while connecting to a launchpad branch with bazaar. After an "ssh-add" it works. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I also had this problem in Karmic while connecting to a launchpad branch with bazaar. After an "ssh-add" it works. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I'm running Intrepid, and like zcrar70 did not have the problem under Hardy. I've found if I close the first dialog box twice, and the Ctl-C the command-line, the next time I try it it works fine. Weird. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I too am experiencing the same bug. Running 8.10, 64-bit on a Core2Duo. This bug first appeared when I changed the passphrase for my key, everything was working fine before that. The workarounds above worked fine for me, and my ssh -v output is the same as well. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Interestingly, restarting X causes this bug to go away. For those experiencing this bug, did it "just show up one day", or did you do something out of the ordinary (eg, change keys, change your passphrase, in any way modify your ~/.ssh directory while running, perhaps deny the keyring once - anything out of the ordinary)? -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
In my case, it happened after upgrading to Intrepid - no passphrase or key changes or anything else out of the ordinary that I remember. I am still getting the error. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Like zcrar70, I'm pretty sure mine started when I upgraded to Intrepid. No passphrase or key changes. Nothing else out of the ordinary that I recall. No denying keyring. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
This started happening to me "out of the blue" on Jaunty amd64. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I just began having this problem in Jaunty amd64 as well. It was working fine as of last night, but today I run into this. I should note that I can use sftp via gnome/gvfs/(whatever the exact program that handles sftp in gnome is) with the exact same key to the same server. Also, if I open seahorse -> select my private key -> Configure key for secure shell -> enter in required information, seahorse gives me the same error message as the terminal ssh client. The SSH_AUTH_SOCK=0 workaround fixed my problem. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I ended up doing this: gconftool-2 --set -t bool /apps/gnome-keyring/daemon-components/ssh false Fixed my problem once I logged out/in. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Marking confirmed, I'm experiencing this problem now on Jaunty as well. :-Dustin ** Changed in: openssh (Ubuntu) Status: New => Confirmed -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Interestingly, if I regenerate my keypair, the new ones work. I'm using a 4096 bit rsa key. My system is an up-to-date Jaunty amd64 install. Also, the new, working key appears to be 4 bytes shorter... $ wc id_rsa orig/id_rsa 51 57 3239 id_rsa 51 57 3243 orig/id_rsa :-Dustin -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
the jaunty issue is likely a different one -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
** Tags added: regression-potential ** Tags removed: regression-potential -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Hi Sebastien, How we can help diagnose the problem? The issue description is wrong (since earlier commentators indicated that it also failed on amd64). I have an i386 and amd64 machine and am only expericing this issue on the amd64 one. Thanks, Anand -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Running into this on intrepid. I have two keys loaded into my gnome- keyring agent, one DSA, one RSA. Pubkey auth using the DSA is key is failing with the "Agent admitted failure" message, but RSA succeeds immediately after. Ran an strace, and noticed that it's writing the following to syslog: Feb 12 20:13:12 timlaptop gnome-keyring-daemon[6368]: signing of the data failed: Invalid object -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Decided to try Tim Utschig's approach and lose the DSA key I'm no longer using, with no positive outcome. Interesting observation, though, and one I hadn't considered. One addition to this that may or may not be unique to my machine. When I first attempt an ssh, the dialog box that pops up reads: "Unlock login keyring Enter login password to unlock keyring Your login keyring was not automatically unlocked when you logged into this computer Password" No matter what I put in there, no joy. But if I close that dialog box using the X in the corner, the next dialog box that pops up reads: "Unlock private key An application wants access to the private key 'id_rsa', but it is locked. Password" When I then enter the key's password in that 2nd dialogue box, everything works fine. So for me, the problem seems to exist with the first issue, where it's unlocking what it calls my "login keyring". Can anyone help clarify this for me? Is that portion something I can easily disable without disabling the 2nd portion? Or is there a way to set the password for that "login keyring"? Unca Xitron -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I have had the problem on my upgraded from Intrepid Jaunty installation. It seems to be that gnome-keyring has a problem while reading my private key in dos format (CR/LF). After converting it to unix format it works like a charm. I've used dos2unix (tofrodos package) to do the job. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Jaunty issues continue: SSH_AUTH_SOCK=0 ssh offers a temporary fix, but ssh-add fixes for good - is there any way to make this process automatic - say - I'm using a new key, prompt user to ok the ssh-add (dont do behind the scenes), and all fixed and done? Il -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Confirm. After an "ssh-add" push to bazaar works. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Hello. Same problem on a recently reinstalled Jaunty. Informations : Architecture : i386 Release : 9.04 Packages version: dpkg -l | grep seahorse ii libcryptui02.26.1-0ubuntu1 ii seahorse 2.26.1-0ubuntu1 ii seahorse-plugins 2.26.1-0ubuntu1 System is up to date. One thing though : we kept user's home when we reinstalled his computer. BUT we removed all his preferences : for dir in .gconf .gconfd .gnome .gnome2 .gnome2_private .local .config do rm -r $HOME/$dir done When we do a "ssh-add", it works again. I tried to do Christian Albrecht fix, but it didn't work on this computer. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I'm having the same exact problem, and the SSH_AUTH_SOCK=0 fix works. I'd remove all my config files like previously posted, but I don't want to reconfigure everything. I've tried search all of the folders Cédric Jeanneret said were deleted for SSH_AUTH_SOCK and even SSH, but turned up nothing. The search was peformed with grep -riHn 'ssh_auth_sock' /folder/path Any other suggestions on what to do and or search for? -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I am also getting this error on an AMD64 machine. The error message I get is still "Agent admitted failure to sign using the key", although the output of ssh -v is a little different - here it is up to when it prompts me to use a password to login: OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /home/nick/.ssh/config debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to nick-curry.com [74.86.89.209] port 22. debug1: Connection established. debug1: identity file /home/nick/.ssh/identity type -1 debug1: identity file /home/nick/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/nick/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1 debug1: match: OpenSSH_3.9p1 pat OpenSSH_3.* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-3ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'nick-curry.com' is known and matches the RSA host key. debug1: Found key in /home/nick/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information No credentials cache found debug1: Unspecified GSS failure. Minor code may provide more information No credentials cache found debug1: Unspecified GSS failure. Minor code may provide more information debug1: Next authentication method: publickey debug1: Offering public key: /home/nick/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 277 Agent admitted failure to sign using the key. debug1: Trying private key: /home/nick/.ssh/identity debug1: Trying private key: /home/nick/.ssh/id_dsa debug1: Next authentication method: password @'s password: -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I forgot to mention, I'm using Intrepid and I wasn't getting this error on Hardy (though I may not have had the latest version of seahorse or gnome-keyring, as I had update-manager disabled for a while). -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Sam, as the original bug reporter, can you confirm that you are also on a big endian machine like PowerPC? ** Summary changed: - ssh Agent admitted failure to sign using the key + ssh Agent admitted failure to sign using the key on big endian machines -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I am experiencing this bug on an amd64 machine. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
My ssh error message looks quite different than the original reporter's now. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
i was on powerpc (big endian). -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Hello. Same problem on a recently reinstalled Jaunty. Informations : Architecture : i386 Release : 9.04 Packages version: dpkg -l | grep seahorse ii libcryptui02.26.1-0ubuntu1 ii seahorse 2.26.1-0ubuntu1 ii seahorse-plugins 2.26.1-0ubuntu1 System is up to date. One thing though : we kept user's home when we reinstalled his computer. BUT we removed all his preferences : for dir in .gconf .gconfd .gnome .gnome2 .gnome2_private .local .config do rm -r $HOME/$dir done When we do a "ssh-add", it works again. I tried to do Christian Albrecht fix, but it didn't work on this computer. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Sam, as the original bug reporter, can you confirm that you are also on a big endian machine like PowerPC? ** Summary changed: - ssh Agent admitted failure to sign using the key + ssh Agent admitted failure to sign using the key on big endian machines -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I am experiencing this bug on an amd64 machine. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
My ssh error message looks quite different than the original reporter's now. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
i was on powerpc (big endian). -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I am also getting this error on an AMD64 machine. The error message I get is still "Agent admitted failure to sign using the key", although the output of ssh -v is a little different - here it is up to when it prompts me to use a password to login: OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /home/nick/.ssh/config debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to nick-curry.com [74.86.89.209] port 22. debug1: Connection established. debug1: identity file /home/nick/.ssh/identity type -1 debug1: identity file /home/nick/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/nick/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1 debug1: match: OpenSSH_3.9p1 pat OpenSSH_3.* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-3ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'nick-curry.com' is known and matches the RSA host key. debug1: Found key in /home/nick/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information No credentials cache found debug1: Unspecified GSS failure. Minor code may provide more information No credentials cache found debug1: Unspecified GSS failure. Minor code may provide more information debug1: Next authentication method: publickey debug1: Offering public key: /home/nick/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 277 Agent admitted failure to sign using the key. debug1: Trying private key: /home/nick/.ssh/identity debug1: Trying private key: /home/nick/.ssh/id_dsa debug1: Next authentication method: password @'s password: -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I forgot to mention, I'm using Intrepid and I wasn't getting this error on Hardy (though I may not have had the latest version of seahorse or gnome-keyring, as I had update-manager disabled for a while). -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
This started happening to me "out of the blue" on Jaunty amd64. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I just began having this problem in Jaunty amd64 as well. It was working fine as of last night, but today I run into this. I should note that I can use sftp via gnome/gvfs/(whatever the exact program that handles sftp in gnome is) with the exact same key to the same server. Also, if I open seahorse -> select my private key -> Configure key for secure shell -> enter in required information, seahorse gives me the same error message as the terminal ssh client. The SSH_AUTH_SOCK=0 workaround fixed my problem. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I ended up doing this: gconftool-2 --set -t bool /apps/gnome-keyring/daemon-components/ssh false Fixed my problem once I logged out/in. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Marking confirmed, I'm experiencing this problem now on Jaunty as well. :-Dustin ** Changed in: openssh (Ubuntu) Status: New => Confirmed -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Interestingly, if I regenerate my keypair, the new ones work. I'm using a 4096 bit rsa key. My system is an up-to-date Jaunty amd64 install. Also, the new, working key appears to be 4 bytes shorter... $ wc id_rsa orig/id_rsa 51 57 3239 id_rsa 51 57 3243 orig/id_rsa :-Dustin -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
the jaunty issue is likely a different one -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
** Tags added: regression-potential ** Tags removed: regression-potential -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Hi Sebastien, How we can help diagnose the problem? The issue description is wrong (since earlier commentators indicated that it also failed on amd64). I have an i386 and amd64 machine and am only expericing this issue on the amd64 one. Thanks, Anand -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Running into this on intrepid. I have two keys loaded into my gnome- keyring agent, one DSA, one RSA. Pubkey auth using the DSA is key is failing with the "Agent admitted failure" message, but RSA succeeds immediately after. Ran an strace, and noticed that it's writing the following to syslog: Feb 12 20:13:12 timlaptop gnome-keyring-daemon[6368]: signing of the data failed: Invalid object -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Decided to try Tim Utschig's approach and lose the DSA key I'm no longer using, with no positive outcome. Interesting observation, though, and one I hadn't considered. One addition to this that may or may not be unique to my machine. When I first attempt an ssh, the dialog box that pops up reads: "Unlock login keyring Enter login password to unlock keyring Your login keyring was not automatically unlocked when you logged into this computer Password" No matter what I put in there, no joy. But if I close that dialog box using the X in the corner, the next dialog box that pops up reads: "Unlock private key An application wants access to the private key 'id_rsa', but it is locked. Password" When I then enter the key's password in that 2nd dialogue box, everything works fine. So for me, the problem seems to exist with the first issue, where it's unlocking what it calls my "login keyring". Can anyone help clarify this for me? Is that portion something I can easily disable without disabling the 2nd portion? Or is there a way to set the password for that "login keyring"? Unca Xitron -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I'm running Intrepid, and like zcrar70 did not have the problem under Hardy. I've found if I close the first dialog box twice, and the Ctl-C the command-line, the next time I try it it works fine. Weird. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I too am experiencing the same bug. Running 8.10, 64-bit on a Core2Duo. This bug first appeared when I changed the passphrase for my key, everything was working fine before that. The workarounds above worked fine for me, and my ssh -v output is the same as well. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Interestingly, restarting X causes this bug to go away. For those experiencing this bug, did it "just show up one day", or did you do something out of the ordinary (eg, change keys, change your passphrase, in any way modify your ~/.ssh directory while running, perhaps deny the keyring once - anything out of the ordinary)? -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
In my case, it happened after upgrading to Intrepid - no passphrase or key changes or anything else out of the ordinary that I remember. I am still getting the error. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Like zcrar70, I'm pretty sure mine started when I upgraded to Intrepid. No passphrase or key changes. Nothing else out of the ordinary that I recall. No denying keyring. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I'm running Intrepid, and like zcrar70 did not have the problem under Hardy. I've found if I close the first dialog box twice, and the Ctl-C the command-line, the next time I try it it works fine. Weird. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I too am experiencing the same bug. Running 8.10, 64-bit on a Core2Duo. This bug first appeared when I changed the passphrase for my key, everything was working fine before that. The workarounds above worked fine for me, and my ssh -v output is the same as well. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Interestingly, restarting X causes this bug to go away. For those experiencing this bug, did it "just show up one day", or did you do something out of the ordinary (eg, change keys, change your passphrase, in any way modify your ~/.ssh directory while running, perhaps deny the keyring once - anything out of the ordinary)? -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
In my case, it happened after upgrading to Intrepid - no passphrase or key changes or anything else out of the ordinary that I remember. I am still getting the error. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Like zcrar70, I'm pretty sure mine started when I upgraded to Intrepid. No passphrase or key changes. Nothing else out of the ordinary that I recall. No denying keyring. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Hi again, Searching some informations on seahorse' ssh-agent, I found this thing: """/!\ Note: This only applies to versions of Seahorse prior to 2.22. In 2.22 and later a full SSH agent is included in gnome-keyring and the agent proxy in Seahorse has been retired. """ maybe there are some problems with versions of those programmes in ubuntu? See source: http://live.gnome.org/Seahorse/SSHAgent Regards, C. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Still present in Jaunty. Using SSH_AUTH_SOCK=0 still works around it. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Hello. Same problem on a recently reinstalled Jaunty. Informations : Architecture : i386 Release : 9.04 Packages version: dpkg -l | grep seahorse ii libcryptui02.26.1-0ubuntu1 ii seahorse 2.26.1-0ubuntu1 ii seahorse-plugins 2.26.1-0ubuntu1 System is up to date. One thing though : we kept user's home when we reinstalled his computer. BUT we removed all his preferences : for dir in .gconf .gconfd .gnome .gnome2 .gnome2_private .local .config do rm -r $HOME/$dir done When we do a "ssh-add", it works again. I tried to do Christian Albrecht fix, but it didn't work on this computer. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I'm having the same exact problem, and the SSH_AUTH_SOCK=0 fix works. I'd remove all my config files like previously posted, but I don't want to reconfigure everything. I've tried search all of the folders Cédric Jeanneret said were deleted for SSH_AUTH_SOCK and even SSH, but turned up nothing. The search was peformed with grep -riHn 'ssh_auth_sock' /folder/path Any other suggestions on what to do and or search for? -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I just began having this problem in Jaunty amd64 as well. It was working fine as of last night, but today I run into this. I should note that I can use sftp via gnome/gvfs/(whatever the exact program that handles sftp in gnome is) with the exact same key to the same server. Also, if I open seahorse -> select my private key -> Configure key for secure shell -> enter in required information, seahorse gives me the same error message as the terminal ssh client. The SSH_AUTH_SOCK=0 workaround fixed my problem. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I ended up doing this: gconftool-2 --set -t bool /apps/gnome-keyring/daemon-components/ssh false Fixed my problem once I logged out/in. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Marking confirmed, I'm experiencing this problem now on Jaunty as well. :-Dustin ** Changed in: openssh (Ubuntu) Status: New => Confirmed -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Interestingly, if I regenerate my keypair, the new ones work. I'm using a 4096 bit rsa key. My system is an up-to-date Jaunty amd64 install. Also, the new, working key appears to be 4 bytes shorter... $ wc id_rsa orig/id_rsa 51 57 3239 id_rsa 51 57 3243 orig/id_rsa :-Dustin -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
the jaunty issue is likely a different one -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
** Tags added: regression-potential ** Tags removed: regression-potential -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Hi Sebastien, How we can help diagnose the problem? The issue description is wrong (since earlier commentators indicated that it also failed on amd64). I have an i386 and amd64 machine and am only expericing this issue on the amd64 one. Thanks, Anand -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Running into this on intrepid. I have two keys loaded into my gnome- keyring agent, one DSA, one RSA. Pubkey auth using the DSA is key is failing with the "Agent admitted failure" message, but RSA succeeds immediately after. Ran an strace, and noticed that it's writing the following to syslog: Feb 12 20:13:12 timlaptop gnome-keyring-daemon[6368]: signing of the data failed: Invalid object -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Decided to try Tim Utschig's approach and lose the DSA key I'm no longer using, with no positive outcome. Interesting observation, though, and one I hadn't considered. One addition to this that may or may not be unique to my machine. When I first attempt an ssh, the dialog box that pops up reads: "Unlock login keyring Enter login password to unlock keyring Your login keyring was not automatically unlocked when you logged into this computer Password" No matter what I put in there, no joy. But if I close that dialog box using the X in the corner, the next dialog box that pops up reads: "Unlock private key An application wants access to the private key 'id_rsa', but it is locked. Password" When I then enter the key's password in that 2nd dialogue box, everything works fine. So for me, the problem seems to exist with the first issue, where it's unlocking what it calls my "login keyring". Can anyone help clarify this for me? Is that portion something I can easily disable without disabling the 2nd portion? Or is there a way to set the password for that "login keyring"? Unca Xitron -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
This started happening to me "out of the blue" on Jaunty amd64. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I have had the problem on my upgraded from Intrepid Jaunty installation. It seems to be that gnome-keyring has a problem while reading my private key in dos format (CR/LF). After converting it to unix format it works like a charm. I've used dos2unix (tofrodos package) to do the job. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I'm having the same exact problem, and the SSH_AUTH_SOCK=0 fix works. I'd remove all my config files like previously posted, but I don't want to reconfigure everything. I've tried search all of the folders Cédric Jeanneret said were deleted for SSH_AUTH_SOCK and even SSH, but turned up nothing. The search was peformed with grep -riHn 'ssh_auth_sock' /folder/path Any other suggestions on what to do and or search for? -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I have had the problem on my upgraded from Intrepid Jaunty installation. It seems to be that gnome-keyring has a problem while reading my private key in dos format (CR/LF). After converting it to unix format it works like a charm. I've used dos2unix (tofrodos package) to do the job. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Hi again, Searching some informations on seahorse' ssh-agent, I found this thing: """/!\ Note: This only applies to versions of Seahorse prior to 2.22. In 2.22 and later a full SSH agent is included in gnome-keyring and the agent proxy in Seahorse has been retired. """ maybe there are some problems with versions of those programmes in ubuntu? See source: http://live.gnome.org/Seahorse/SSHAgent Regards, C. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Still present in Jaunty. Using SSH_AUTH_SOCK=0 still works around it. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I also had this problem in karmic while connecting to a launchpad branch with bazaar. After an "ssh-add" it works. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I also had this problem in Karmic while connecting to a launchpad branch with bazaar. After an "ssh-add" it works. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Jaunty issues continue: SSH_AUTH_SOCK=0 ssh offers a temporary fix, but ssh-add fixes for good - is there any way to make this process automatic - say - I'm using a new key, prompt user to ok the ssh-add (dont do behind the scenes), and all fixed and done? Il -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Confirm. After an "ssh-add" push to bazaar works. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Sam, as the original bug reporter, can you confirm that you are also on a big endian machine like PowerPC? ** Summary changed: - ssh Agent admitted failure to sign using the key + ssh Agent admitted failure to sign using the key on big endian machines -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I am experiencing this bug on an amd64 machine. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
My ssh error message looks quite different than the original reporter's now. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
i was on powerpc (big endian). -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I am also getting this error on an AMD64 machine. The error message I get is still "Agent admitted failure to sign using the key", although the output of ssh -v is a little different - here it is up to when it prompts me to use a password to login: OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /home/nick/.ssh/config debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to nick-curry.com [74.86.89.209] port 22. debug1: Connection established. debug1: identity file /home/nick/.ssh/identity type -1 debug1: identity file /home/nick/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/nick/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1 debug1: match: OpenSSH_3.9p1 pat OpenSSH_3.* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-3ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'nick-curry.com' is known and matches the RSA host key. debug1: Found key in /home/nick/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information No credentials cache found debug1: Unspecified GSS failure. Minor code may provide more information No credentials cache found debug1: Unspecified GSS failure. Minor code may provide more information debug1: Next authentication method: publickey debug1: Offering public key: /home/nick/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 277 Agent admitted failure to sign using the key. debug1: Trying private key: /home/nick/.ssh/identity debug1: Trying private key: /home/nick/.ssh/id_dsa debug1: Next authentication method: password @'s password: -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I forgot to mention, I'm using Intrepid and I wasn't getting this error on Hardy (though I may not have had the latest version of seahorse or gnome-keyring, as I had update-manager disabled for a while). -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Sam, as the original bug reporter, can you confirm that you are also on a big endian machine like PowerPC? ** Summary changed: - ssh Agent admitted failure to sign using the key + ssh Agent admitted failure to sign using the key on big endian machines -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I am experiencing this bug on an amd64 machine. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
My ssh error message looks quite different than the original reporter's now. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
i was on powerpc (big endian). -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Jaunty issues continue: SSH_AUTH_SOCK=0 ssh offers a temporary fix, but ssh-add fixes for good - is there any way to make this process automatic - say - I'm using a new key, prompt user to ok the ssh-add (dont do behind the scenes), and all fixed and done? Il -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Confirm. After an "ssh-add" push to bazaar works. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Sam, as the original bug reporter, can you confirm that you are also on a big endian machine like PowerPC? ** Summary changed: - ssh Agent admitted failure to sign using the key + ssh Agent admitted failure to sign using the key on big endian machines -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I am experiencing this bug on an amd64 machine. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
My ssh error message looks quite different than the original reporter's now. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
i was on powerpc (big endian). -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I'm running Intrepid, and like zcrar70 did not have the problem under Hardy. I've found if I close the first dialog box twice, and the Ctl-C the command-line, the next time I try it it works fine. Weird. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
I too am experiencing the same bug. Running 8.10, 64-bit on a Core2Duo. This bug first appeared when I changed the passphrase for my key, everything was working fine before that. The workarounds above worked fine for me, and my ssh -v output is the same as well. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
Interestingly, restarting X causes this bug to go away. For those experiencing this bug, did it "just show up one day", or did you do something out of the ordinary (eg, change keys, change your passphrase, in any way modify your ~/.ssh directory while running, perhaps deny the keyring once - anything out of the ordinary)? -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
In my case, it happened after upgrading to Intrepid - no passphrase or key changes or anything else out of the ordinary that I remember. I am still getting the error. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 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
