Comment 25 for bug 201786

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.