gnome-keyring-daemon [16231]: algoritmo de chave não suportado no certificado: 1.2.840.10045.2.1

Question

Ok ... então, quando tento acessar a conta shell do serviço de hospedagem, não consigo fazer login. O problema parece ser o serviço Gnome Keyring não ter um algoritmo de chave suportado, mas eu não tenho a menor idéia de como consertar isso e estou perdendo muito tempo pesquisando por respostas que ninguém parece ter. Um site disse que instalar o pacote libpam-unix2 deve corrigir o problema, mas não consertou nada para mim.

Espero que alguém aqui tenha uma pista. Aqui está o que está acontecendo (estou usando o Ubuntu 12.04) ....

$ rm -R .ssh
$ ssh -v ###.###.###.###
OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ###.###.###.### [###.###.###.###] port 22.
debug1: Connection established.
debug1: SELinux support disabled
debug1: identity file /home/forrest/.ssh/id_rsa type -1
debug1: identity file /home/forrest/.ssh/id_rsa-cert type -1
debug1: identity file /home/forrest/.ssh/id_dsa type -1
debug1: identity file /home/forrest/.ssh/id_dsa-cert type -1
debug1: identity file /home/forrest/.ssh/id_ecdsa type -1
debug1: identity file /home/forrest/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr 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: Server host key: RSA f4:a8:f7:88:56:bd:6e:87:73:3d:45:12:8d:c2:eb:c0
The authenticity of host '###.###.###.### (###.###.###.###)' can't be established.
RSA key fingerprint is f4:a8:f7:88:56:bd:6e:87:73:3d:45:12:8d:c2:eb:c0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '###.###.###.###' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/forrest/.ssh/id_rsa
debug1: Trying private key: /home/forrest/.ssh/id_dsa
debug1: Trying private key: /home/forrest/.ssh/id_ecdsa
debug1: Next authentication method: password
forrest@###.###.###.###'s password: 
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
forrest@###.###.###.###'s password: 
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
forrest@###.###.###.###'s password: 
debug1: Authentications that can continue: publickey,password
debug1: No more authentication methods to try.
Permission denied (publickey,password).

O bit relevante em /var/logs/auth.log diz -

Aug 11 09:01:17 pompano gnome-keyring-daemon[16231]: unsupported key algorithm in certificate: 1.2.840.10045.2.1
Aug 11 09:02:33  gnome-keyring-daemon[16231]: last message repeated 4 times

Então aparentemente o chaveiro gnome não tem mais o algoritmo de chave suportado para o SSH? Huh?

    

Answer 1

A postagem de John S Gruber deveria ajudar. Faça:

env | grep SSH_AUTH_SOCK

Verifique o valor da variável para ver se esse arquivo existe. Se isso acontecer:

unset SSH_AUTH_SOCK

Isso deve remover o arquivo de soquete; se não, você pode precisar removê-lo manualmente (como sudo).