[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Hi Petrida, could you please elaborate on why you changed the bug status from incomplete to confirmed without providing the requested information from comment #95? ** Changed in: openssh (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

According to https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1420522 it's fixed in seahorse 3.30, which is present in ubuntu cosmic and later. >From https://bugzilla.redhat.com/show_bug.cgi?id=1435924, this should >reproduce the problem: 1. Generate a ssh key using the keytype ed25519

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Peter: Yes, that's all true (it's a workaround after all), though you could add the ssh-agent command to your startup scripts. I've updated my Stack Exchange answer to reflect that. BTW, you don't actually need the `mv` line since the .broken

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

While this is not a big endian problem, it is a problem and it is NOT solved yet. I doubt it will be solved until Ubuntu bug 1420522 is solved. This is GNOME bug 754028 (Among

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

** Tags added: 14.04 ** Tags added: 14.10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big endian machines

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

The workaround of the following commands only works until I log out (not restarting the computer): mv $SSH_AUTH_SOCK $SSH_AUTH_SOCK.broken ssh-agent -a $SSH_AUTH_SOCK ssh-add When I log back in, without having to restart the computer, the SSH_AUTH_SOCK is corrupted again, and it seems to be

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Summary of problem (for me): * ssh host fails with ssh Agent admitted failure * SSH_AUTH_SOCK= ssh host works just fine * Conclusion: gnome-keyring can't deal with complex keys WORKAROUND: mv $SSH_AUTH_SOCK $SSH_AUTH_SOCK.broken ssh-agent -a $SSH_AUTH_SOCK This is a new instance of

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I woke up this morning, and I get this error message. What happened? -- it was working last night. -- ssh-add -l says everything is there. -- above means that ssh-agent is running -- contents of /tmp and /tmp/keyring-XXX look OK -- SSH_AUTH_SOCK=0 ssh wherever works System: ubuntu 14.04 Uptime:

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

For some reason this problem just cropped up for me on 12.04.1 As of last week the problem didnt exist, I believe something must have caused this in the last set of updates I installed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Actually, interestingly I just found: ps aux | grep ssh-agent madmaze 23158 0.0 0.0 13600 920 pts/8R+ 20:24 0:00 grep --color=auto ssh-agent madmaze 24080 0.0 0.0 0 0 ?Zs Nov02 0:14 [ssh-agent] defunct I tried restarting ssh-agent but problem persists.

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

it seems after a reboot it fixed itself again, so I assume it crashed for some reason. I greped through /var/log for any indication of what caused the crash.. found nothing. consider this resolved for me. -- You received this bug notification because you are a member of Ubuntu Server Team,

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

same problem in 12.04. unset SSH_AUTH_SOCK worked. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big endian

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I encountered this problem after upgrading to Precise 12.04 LTS -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Same bug on 11.10, ssh-add solved it for me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big endian machines

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

same problem in 12.04 ssh-add doesn't help, but SSH_AUTH_SOCK=0 works -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Not sure if this is the same. Connecting to my dreamplug running Ubuntu 9.04 from my laptop running 11.10 I'm getting the following (using ssh -vv) debug1: Authentications that can continue: publickey debug1: Offering DSA public key: app_81@localhost debug2: we sent a publickey packet,

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

This bug affects 11.10 too. Creating the key with a type different from rsa, e.g. dsa, fixes the problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

yes 11.10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big endian machines To manage notifications about this

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Confirming on 11.10 also, setting SSH_AUTH_SOCK = 0 works. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Confirming this bug on Ubuntu 11.04 as on 6th August 2011 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I have the same bug on 11.04, and can confirm that either setting SSH_AUTH_SOCK = 0, or deleting the directory it is pointing to (/tmp /keyring-something) solves the problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Had the same issue in 10.04 LTS. ssh-add resolved it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big endian

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

** Changed in: gnome-keyring (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) = ANDI MUHAMMAD HARPIANTO (amhnews) ** Changed in: gnome-keyring (Ubuntu) Assignee: ANDI MUHAMMAD HARPIANTO (amhnews) = (unassigned) -- You received this bug notification because you are a member of

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I am having this same issue in Natty. In fact, this problem only occured after upgrading to Natty. Installing seahorse-plugins did not resolve the issue. Running ssh-add did resolve the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

** Changed in: seahorse Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

$ lsb_release -r Release:10.10 $ uname -a Linux milhouse 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 11:55:36 UTC 2010 x86_64 GNU/Linux $ ssh -v robert@remotehost OpenSSH_5.5p1 Debian-4ubuntu5, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1:

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I'd like to confirm this bug too when using an SSH key with no passphrase. I'm able to override the issue by running SSH_AUTH_SOCK=0 ssh -v user@host Description:Ubuntu 10.04.1 LTS Release:10.04 Codename: lucid -- You received this bug notification because you are a member of

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I should note that this x86_64 and so clearly it's not a big endian bug for my machine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

If I install 'seahorse-plugins', I'm still not able to use this key and account without modifying SSH_AUTH_SOCK. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

same problem for me for maverick x86 ( at both ends) I think its to do with generating key and then replacing it -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I don't think this problem is related to big-endianness. I just had it on a x86 system that was upgraded from feisty - hardy - lucid. In my case the fix was simple: apt-get install seahorse-plugins. For whatever reason that dependency doesn't seem to be pulled in when you upgrade. I'd recommend

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I have the same problem in Maverick -- 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 Server Team, which is subscribed to openssh in ubuntu. --

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I am experiencing this bug in Lucid when trying to connect (push) to github. Running: ssh-add Solves works-around the problem for the session, in a terminal. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 You received this bug

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I had a similiar problem and I solved it with: [srydb...@zeus ~]$ echo $SSH_AUTH_SOCK /tmp/keyring-KXX3Aw/ssh [srydb...@zeus tmp]$ sudo rm -rf keyring-KXX3Aw/ Maybe the keys are cached there? -- ssh Agent admitted failure to sign using the key on big endian machines

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I also came across with the above error message while using ssh. I tried ssh in 2 machines in a loop. Only 1 showed(machine 21, below) the error. And in that machine(21)i had changed the password once before i ssh. So i think the error may be because of the password change. Please note that

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

It was Ok when I installed openSSH on this May as soon as ubuntu 10.04 LTS came out. It encountered the same problem as described above when I make another new installation this afternoon. It was resolved after runnig ssh-add ~/.ssh/id_rsa as said on these comments. I found out another thing

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

The same problems. After SSH_AUTH_SOCK=0 all works fine. -- 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 Server Team, which is subscribed to openssh in ubuntu.

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

** Changed in: seahorse Importance: Unknown = Critical -- 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 Server Team, which is subscribed to openssh in ubuntu.

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Got the same problem here, fixed it by running ssh-add after key creation thanks to Portable-Jim -- 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 Server Team,

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Same problem: iBook G4 (PPC) Ubuntu 10.04 Lucid Lynx Order of events: 1. Switched from Debian. Copied home. - Problem appeared 2. Re-created keys and copied key across to authorised keys - Problem persisted 3. Deleted all keys, regenerated and copied key across to authorised keys - Problem

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

same here, out of the box lucid. , the ssh-add didn't solve the problem. the SSH_AUTH_SOCK=0 added to the bashrc file works, but it still is a pain -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 You received this bug notification

Re: [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Just my $0.02... If you use an SSH agent, do yourself a favor and use OpenSSH's own ssh-agent. I've found seahorse/gnome-keyring-daemon/whatever very unreliable, especially when I run dozens of parallel ssh commands (which all use public key auth via the SSH agent). I give it a chance with

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

This one bit me when I deleted my old ssh keys and generated new ones on Karmic. Both work-arounds worked for me (I tried them individually)--adding the line export SSH_AUTH_SOCK=0 to ~/.bashrc OR running ssh-add ~/.ssh/id_rsa. I like the latter better because it doesn't require extra work to

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I had this problem today, with Karmic. The problem went away after a logged out and logged back in - I'm not sure what the problem is with older versions, but I think in Karmic the problem is that seahorse does not update with the new key when a new key is created while it is running. If you try

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Utterly annoying. As a workaround put line export SSH_AUTH_SOCK=0 to /home/YOURUSERNAME/.bashrc file. Works for terminal sessions only, though. -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 You received this bug

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I concur... this is a problem that should have been fixed by now. When I run export SSH_AUTH_SOCK=0 on the host machine, I have no problem connecting to the target system after placing the key in the authorized_keys2 file (on target). Note: This must be done for each and every shell opened on the

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Same problem in karmic. I found this solution : export SSH_AUTH_SOCK=0 It's works fine. -- 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 Server Team, which is

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I ran into this same problem in Karmic. Using 'ssh-add ~/.ssh/id_rsa' on the machine I am trying to connect with fixed the 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

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I get this on Gentoo amd64. SSH_AUTH_SOCK=0 workaround works fine. Just weird, I don't recall wanting this feature in SSH and there doesn't seem to be an option to make it not do this. -- ssh Agent admitted failure to sign using the key on big endian machines

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

I had the same problem in Ubuntu 9.04 the problem was solved with gconftool-2 --set -t bool /apps/gnome- keyring/daemon-components/ssh false -- ssh Agent admitted failure to sign using the key on big endian machines https://bugs.launchpad.net/bugs/201786 You received this bug notification

[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 Server Team, which is subscribed to openssh in ubuntu. --

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Jaunty issues continue: SSH_AUTH_SOCK=0 ssh host 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

[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

[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

[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

[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 Server Team, which is subscribed to

[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

[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

[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

[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 Server Team, which is subscribed to openssh in ubuntu. --

[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 Server Team, which is subscribed to

[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

Re: [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

The new problem being experienced on Jaunty has been split out to Bug #328445. :-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 Server Team, which is

[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:

[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 Server Team, which is subscribed to openssh in

[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

[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

[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

[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

[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

[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

[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 -

[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

[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