linux – 为什么SSHD挂在“服务器接受密钥”

概述我使用公钥认证一年来一直没有问题. 没有对客户端或服务器的ssh配置进行任何更改.现在,ssh连接永远不会完成或失败,它们只是挂起.以下是尝试连接时的调试输出： OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012debug1: Reading configuration data /home/jivan/.ssh/configde 我使用公钥认证一年来一直没有问题.

没有对客户端或服务器的ssh配置进行任何更改.现在,ssh连接永远不会完成或失败,它们只是挂起.以下是尝试连接时的调试输出：

OpenSSH_6.0p1 Debian-3ubuntu1,OpenSSL 1.0.1c 10 May 2012deBUG1: Reading configuration data /home/jivan/.ssh/configdeBUG1: Reading configuration data /etc/ssh/ssh_configdeBUG1: /etc/ssh/ssh_config line 19: Applying options for *deBUG1: Connecting to <host> [<ip>] port <port>.deBUG1: Connection established.deBUG1: IDentity file .ssh/ID_rsa.pub type 1deBUG1: Checking blackList file /usr/share/ssh/blackList.RSA-2048deBUG1: Checking blackList file /etc/ssh/blackList.RSA-2048deBUG1: IDentity file .ssh/ID_rsa.pub-cert type -1deBUG1: Remote protocol version 2.0,remote software version OpenSSH_5.8p1 Debian-7ubuntu1deBUG1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH_5*deBUG1: Enabling compatibility mode for protocol 2.0deBUG1: Local version string SSH-2.0-OpenSSH_6.0p1 Debian-3ubuntu1deBUG1: SSH2_MSG_KEXINIT sentdeBUG1: SSH2_MSG_KEXINIT receiveddeBUG1: kex: server->clIEnt aes128-ctr hmac-md5 nonedeBUG1: kex: clIEnt->server aes128-ctr hmac-md5 nonedeBUG1: sending SSH2_MSG_KEX_ECDH_INITdeBUG1: expecting SSH2_MSG_KEX_ECDH_REPLYdeBUG1: Server host key: ECDSA 81:63:05:0c:39:6b:77:d7:a2:25:93:30:80:f1:ba:0edeBUG1: Host '[<host>]:<port>' is kNown and matches the ECDSA host key.deBUG1: Found key in /home/jivan/.ssh/kNown_hosts:39deBUG1: ssh_ecdsa_verify: signature correctdeBUG1: SSH2_MSG_NEWKEYS sentdeBUG1: expecting SSH2_MSG_NEWKEYSdeBUG1: SSH2_MSG_NEWKEYS receiveddeBUG1: Roaming not allowed by serverdeBUG1: SSH2_MSG_SERVICE_REQUEST sentdeBUG1: SSH2_MSG_SERVICE_ACCEPT receiveddeBUG1: Authentications that can continue: publickey,passworddeBUG1: Next authentication method: publickeydeBUG1: Offering RSA public key: .ssh/ID_rsa.pubdeBUG1: Server accepts key: pkalg ssh-rsa blen 279

服务器日志：

Feb 24 12:02:38 balance sshd[5734]: deBUG1: Forked child 6745.Feb 24 12:02:38 balance sshd[6745]: Set /proc/self/oom_score_adj to 0Feb 24 12:02:38 balance sshd[6745]: deBUG1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8Feb 24 12:02:38 balance sshd[6745]: deBUG1: inetd sockets after dupPing: 3,3Feb 24 12:02:38 balance sshd[6745]: Connection from 207.204.228.55 port 57967Feb 24 12:02:38 balance sshd[6745]: deBUG1: ClIEnt protocol version 2.0; clIEnt software version OpenSSH_6.0p1 Debian-3ubuntu1Feb 24 12:02:38 balance sshd[6745]: deBUG1: match: OpenSSH_6.0p1 Debian-3ubuntu1 pat OpenSSH*Feb 24 12:02:38 balance sshd[6745]: deBUG1: Enabling compatibility mode for protocol 2.0Feb 24 12:02:38 balance sshd[6745]: deBUG1: Local version string SSH-2.0-OpenSSH_5.8p1 Debian-7ubuntu1Feb 24 12:02:39 balance sshd[6745]: deBUG1: PAM: initializing for "jivan"Feb 24 12:02:39 balance sshd[6745]: deBUG1: PAM: setting PAM_RHOST to "207.204.228.55"Feb 24 12:02:39 balance sshd[6745]: deBUG1: PAM: setting PAM_TTY to "ssh"Feb 24 12:02:40 balance sshd[6745]: deBUG1: Checking blackList file /usr/share/ssh/blackList.RSA-2048Feb 24 12:02:40 balance sshd[6745]: deBUG1: Checking blackList file /etc/ssh/blackList.RSA-2048Feb 24 12:02:40 balance sshd[6745]: deBUG1: temporarily_use_uID: 1000/1000 (e=0/0)Feb 24 12:02:40 balance sshd[6745]: deBUG1: trying public key file /home/jivan/.ssh/authorized_keysFeb 24 12:02:40 balance sshd[6745]: deBUG1: fd 4 clearing O_NONBLOCKFeb 24 12:02:40 balance sshd[6745]: deBUG1: matching key found: file /home/jivan/.ssh/authorized_keys,line 1Feb 24 12:02:40 balance sshd[6745]: Found matching RSA key: 5f:8c:76:ad:48:6a:f5:73:03:6a:36:13:c0:ea:3b:45Feb 24 12:02:40 balance sshd[6745]: deBUG1: restore_uID: 0/0

任何想法可能是什么问题？

更新：
问题在开始时神秘地停止了.仍然对可能导致这种情况的任何见解感兴趣.

解决方法 这通常是由反向DNS问题引起的;这一周发生在我的旧服务器上.你是正确的调用sshd -d,但反向DNS问题不会真正变得明显,除非你用sshd -ddd运行它,以便你看到deBUG3的输出.

虽然反向DNS问题并不总是导致事情严重失败,但如果与连接尝试相关的足够DNS查找失败(即所有DNS服务器完全不可用,或者相关区域/反向区域足够超时),在某些配置下,完全锁定对系统的ssh访问就足够了.如果服务器不耐烦并丢弃连接,则设置客户端超时的高低并不重要.

总结

以上是内存溢出为你收集整理的linux – 为什么SSHD挂在“服务器接受密钥”全部内容，希望文章能够帮你解决linux – 为什么SSHD挂在“服务器接受密钥”所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错，欢迎将内存溢出网站推荐给程序员好友。