Bug #201786 in openssh (Ubuntu): “ssh Agent admitted failure to sign using the key on big endian machines”
Bug #201786 in openssh (Ubuntu): “ssh Agent admitted failure to sign using the key on big endian machines”
This was annoying. Reinstalled Mum's machine with Ubuntu 10.10 but kept home directories intact so should still have been able to ssh.
Putty worked just fine from my notebook, but running ssh on the server seemed to halt forever. Why? It was asking me to unlock the keyring on the X server.
So, if I ran ssh -v -i ~/.ssh/id_rsa_blah myhost.mydomain.com
The last thing that appeared in the ssh session was:
debug1: Server accepts key: pkalg ssh-rsa blen 277
And that was because a nice dialog box had appeared on the X server waiting for me to unlock my passphrase or something (I cant post the dialog box because I cant reproduce it now).
Anyway, as suggested in the link attached running
SSH_AUTH_SOCK=0 ssh -v -i ~/.ssh/id_rsa_blah myhost.mydomain.com
seemed to get me in.
For reference, set | grep SSH_AUTH_SOCK yields:
SSH_AUTH_SOCK=/tmp/keyring-NUtSG3/ssh
This was annoying. Reinstalled Mum's machine with Ubuntu 10.10 but kept home directories intact so should still have been able to ssh.
Putty worked just fine from my notebook, but running ssh on the server seemed to halt forever. Why? It was asking me to unlock the keyring on the X server.
So, if I ran ssh -v -i ~/.ssh/id_rsa_blah myhost.mydomain.com
The last thing that appeared in the ssh session was:
debug1: Server accepts key: pkalg ssh-rsa blen 277
And that was because a nice dialog box had appeared on the X server waiting for me to unlock my passphrase or something (I cant post the dialog box because I cant reproduce it now).
Anyway, as suggested in the link attached running
SSH_AUTH_SOCK=0 ssh -v -i ~/.ssh/id_rsa_blah myhost.mydomain.com
seemed to get me in.
For reference, set | grep SSH_AUTH_SOCK yields:
SSH_AUTH_SOCK=/tmp/keyring-NUtSG3/ssh
Comments