Não é possível ssh para localhost usando a chave

Question

Eu configurei uma chave ssh e quero conectar-me ao localhost usando somente a chave, sem senha (nota: isso é apenas um teste; no final eu quero conectar a um servidor git interno, onde o mesmo problema ocorre). Aqui está a saída de ssh -v localhost

OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /home/myusername/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: identity file /home/myusername/.ssh/id_rsa type 1
debug1: identity file /home/myusername/.ssh/id_rsa-cert type -1
debug1: identity file /home/myusername/.ssh/id_dsa type -1
debug1: identity file /home/myusername/.ssh/id_dsa-cert type -1
debug1: identity file /home/myusername/.ssh/id_ecdsa type -1
debug1: identity file /home/myusername/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/myusername/.ssh/id_ed25519 type -1
debug1: identity file /home/myusername/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6 pat OpenSSH_6.6.1* compat 0x04000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr [email protected] none
debug1: kex: client->server aes128-ctr [email protected] none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA 7f:96:64:b2:df:f5:de:e8:af:ff:5d:da:5e:3d:e4:c1
debug1: Host 'localhost' is known and matches the ECDSA host key.
debug1: Found key in /home/myusername/.ssh/known_hosts:12
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
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: Offering RSA public key: /home/myusername/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/myusername/.ssh/id_dsa
debug1: Trying private key: /home/myusername/.ssh/id_ecdsa
debug1: Trying private key: /home/myusername/.ssh/id_ed25519
debug1: Next authentication method: password

Eu li vários posts sobre problemas semelhantes e verifiquei várias dicas:

As permissões
• $ HOME (700), .ssh (700) e .ssh / * (644, exceto authorized_keys e id_rsa, que possuem 600) devem estar corretas
• conectando via senha funciona

Curiosamente, meu computador informa explicitamente que aceita a chave:

debug1: Server accepts key: pkalg ssh-rsa blen 279

Editar: entradas auth.log correspondentes:

May 18 16:34:44 desktop-178 sshd[3330]: error: RSA_public_decrypt failed: error:0407006A:lib(4):func(112):reason(106)
May 18 16:34:52 desktop-178 sshd[3330]: Connection closed by 127.0.0.1 [preauth]

No entanto, no final, pedem minha senha. Como eu resolvo isso?

    

Answer 1

Vou postar isso como uma resposta, porque isso resolve parcialmente o problema, mas não estou satisfeito porque não entendo o que está errado.

Encontrado em: link

If I change the name of the private key to id_rsa.old and then specify it with the -i flag I can then login to the first host.

Posso confirmar que isso funciona, mas isso é um incômodo, na melhor das hipóteses, e francamente confuso.