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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
