Summary: | net-misc/openssh-6.1_p1-r1: ssh login with key hangs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Juergen Rose
2013-01-27 08:27:20 UTC
BTW. If I do as root at impala, 'ssh -vY rose@impala': ... debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_dsa debug1: Trying private key: /root/.ssh/id_ecdsa debug1: Next authentication method: keyboard-interactive Password: debug1: Authentication succeeded (keyboard-interactive). Authenticated to condor ([192.168.1.76]:22). login works like a charm. I just saw, that I missed the last line of the ssh output in my first posting. So, ssh comes until: ... debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: /home/rose/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 434 I have the same issue at the next pairs of computer. I want as rose@leopard open a ssh connection to lynx. It hangs since today: rose@leopard:/home_leopard/rose(9)$ ssh -v rose@lynx OpenSSH_6.1p1-hpn13v11, OpenSSL 1.0.1e 11 Feb 2013 debug1: Reading configuration data /home/rose/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to lynx [192.168.2.11] port 22. debug1: Connection established. debug1: identity file /home/rose/.ssh/id_rsa type -1 debug1: identity file /home/rose/.ssh/id_rsa-cert type -1 debug1: identity file /home/rose/.ssh/id_dsa type 2 debug1: identity file /home/rose/.ssh/id_dsa-cert type -1 debug1: identity file /home/rose/.ssh/id_ecdsa type -1 debug1: identity file /home/rose/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.1p1-hpn13v11 debug1: match: OpenSSH_6.1p1-hpn13v11 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.1p1-hpn13v11 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: AUTH STATE IS 0 debug1: REQUESTED ENC.NAME is 'aes128-ctr' debug1: kex: server->client aes128-ctr hmac-md5 none debug1: REQUESTED ENC.NAME is 'aes128-ctr' debug1: kex: client->server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA 54:57:64:da:e0:57:a1:14:2e:68:41:86:e0:84:17:4c debug1: Host 'lynx' is known and matches the ECDSA host key. debug1: Found key in /home/rose/.ssh/known_hosts:2 debug1: ssh_ecdsa_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,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: /home/rose/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 434 ^C rose@leopard:/home_leopard/rose(10)$ mv /home/rose/.ssh/id_rsa /home/rose/.ssh/_id_rsa If I do the same as root it works: root@leopard:/root(23)# ssh -v rose@lynx OpenSSH_6.1p1-hpn13v11, OpenSSL 1.0.1e 11 Feb 2013 debug1: Reading configuration data /root/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to lynx [192.168.2.11] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.1p1-hpn13v11 debug1: match: OpenSSH_6.1p1-hpn13v11 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.1p1-hpn13v11 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: AUTH STATE IS 0 debug1: REQUESTED ENC.NAME is 'aes128-ctr' debug1: kex: server->client aes128-ctr hmac-md5 none debug1: REQUESTED ENC.NAME is 'aes128-ctr' debug1: kex: client->server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA 54:57:64:da:e0:57:a1:14:2e:68:41:86:e0:84:17:4c debug1: Host 'lynx' is known and matches the ECDSA host key. debug1: Found key in /root/.ssh/known_hosts:3 debug1: ssh_ecdsa_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,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_dsa debug1: Trying private key: /root/.ssh/id_ecdsa debug1: Next authentication method: keyboard-interactive Password: debug1: Authentication succeeded (keyboard-interactive). Authenticated to lynx ([192.168.2.11]:22). debug1: Final hpn_buffer_size = 131072 debug1: HPN Disabled: 0, HPN Buffer Size: 131072 debug1: channel 0: new [client-session] debug1: Enabled Dynamic Window Scaling debug1: Requesting no-more-sessions@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 ... rose@lynx:/home/rose(1)$ Restarting the ssh server at lynx does not change anything. Removing the ssh keys in /home/rose/.ssh does not change anything. It happens not only with lynx at target but also with other computers. Any idea? After reboot the issue disappeared. Could it be, that a crashed gnome-keyring-daemon could be responsible for the last issue? |