我正在尝试使用 PHP SSH2 函数连接到服务器。

这是我正在测试的代码:

if(!($con = ssh2_connect("123.123.123.123", 22))){ 
    echo "fail: unable to establish connection\n"; 
} else { 
    if(!ssh2_auth_password($con, "test", "test")) { 
        echo "fail: unable to authenticate\n"; 
    } else { 
        echo "connected"; 
        ssh2_exec($con, 'exit'); 
        unset($con); 
    } 
} 

我输入的用户名和密码是什么并不重要, ssh2_auth_password()总是返回真。

以下 ssh2_exec只是挂起 PHP 脚本,直到我关闭它。

为什么会发生这种情况?
ssh 的输出对于相同的凭据:

vm@vm ~/ $ ssh -vvvv test@123.123.123.123 
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 * 
debug2: ssh_connect: needpriv 0 
debug1: Connecting to 123.123.123.123 [123.123.123.123] port 22. 
debug1: Connection established. 
debug1: identity file /home/vm/.ssh/id_rsa type -1 
debug1: identity file /home/vm/.ssh/id_rsa-cert type -1 
debug1: identity file /home/vm/.ssh/id_dsa type -1 
debug1: identity file /home/vm/.ssh/id_dsa-cert type -1 
debug1: identity file /home/vm/.ssh/id_ecdsa type -1 
debug1: identity file /home/vm/.ssh/id_ecdsa-cert type -1 
debug1: Remote protocol version 2.0, remote software version dropbear_0.52 
debug1: no match: dropbear_0.52 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 
debug2: fd 3 setting O_NONBLOCK 
debug3: load_hostkeys: loading entries for host "123.123.123.123" from file "/home/vm/.ssh/known_hosts" 
debug3: load_hostkeys: found key type RSA in file /home/vm/.ssh/known_hosts:9 
debug3: load_hostkeys: loaded 1 keys 
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa 
debug1: SSH2_MSG_KEXINIT sent 
debug1: SSH2_MSG_KEXINIT received 
debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-dss 
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se 
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se 
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib 
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: diffie-hellman-group1-sha1 
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss 
debug2: kex_parse_kexinit: aes128-ctr,3des-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes256-cbc,twofish256-cbc,twofish-cbc,twofish128-cbc,blowfish-cbc 
debug2: kex_parse_kexinit: aes128-ctr,3des-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes256-cbc,twofish256-cbc,twofish-cbc,twofish128-cbc,blowfish-cbc 
debug2: kex_parse_kexinit: hmac-sha1-96,hmac-sha1,hmac-md5 
debug2: kex_parse_kexinit: hmac-sha1-96,hmac-sha1,hmac-md5 
debug2: kex_parse_kexinit: zlib,zlib@openssh.com,none 
debug2: kex_parse_kexinit: zlib,zlib@openssh.com,none 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: mac_setup: found hmac-md5 
debug1: kex: server->client aes128-ctr hmac-md5 none 
debug2: mac_setup: found hmac-md5 
debug1: kex: client->server aes128-ctr hmac-md5 none 
debug2: dh_gen_key: priv key bits set: 121/256 
debug2: bits set: 504/1024 
debug1: sending SSH2_MSG_KEXDH_INIT 
debug1: expecting SSH2_MSG_KEXDH_REPLY 
debug1: Server host key: RSA xx:f3:xx:97:xx:b4:xx:2b:xx:e7:xx:87:xx:44:xx:b3 
debug3: load_hostkeys: loading entries for host "123.123.123.123" from file "/home/vm/.ssh/known_hosts" 
debug3: load_hostkeys: found key type RSA in file /home/vm/.ssh/known_hosts:9 
debug3: load_hostkeys: loaded 1 keys 
debug1: Host '123.123.123.123' is known and matches the RSA host key. 
debug1: Found key in /home/vm/.ssh/known_hosts:9 
debug2: bits set: 513/1024 
debug1: ssh_rsa_verify: signature correct 
debug2: kex_derive_keys 
debug2: set_newkeys: mode 1 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug2: set_newkeys: mode 0 
debug1: SSH2_MSG_NEWKEYS received 
debug1: Roaming not allowed by server 
debug1: SSH2_MSG_SERVICE_REQUEST sent 
debug2: service_accept: ssh-userauth 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug2: key: /home/vm/.ssh/id_rsa ((nil)) 
debug2: key: /home/vm/.ssh/id_dsa ((nil)) 
debug2: key: /home/vm/.ssh/id_ecdsa ((nil)) 
debug1: Authentications that can continue: publickey,password 
debug3: start over, passed a different list publickey,password 
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password 
debug3: authmethod_lookup publickey 
debug3: remaining preferred: keyboard-interactive,password 
debug3: authmethod_is_enabled publickey 
debug1: Next authentication method: publickey 
debug1: Trying private key: /home/vm/.ssh/id_rsa 
debug3: no such identity: /home/vm/.ssh/id_rsa 
debug1: Trying private key: /home/vm/.ssh/id_dsa 
debug3: no such identity: /home/vm/.ssh/id_dsa 
debug1: Trying private key: /home/vm/.ssh/id_ecdsa 
debug3: no such identity: /home/vm/.ssh/id_ecdsa 
debug2: we did not send a packet, disable method 
debug3: authmethod_lookup password 
debug3: remaining preferred: ,password 
debug3: authmethod_is_enabled password 
debug1: Next authentication method: password 
test@123.123.123.123's password: 
debug3: packet_send2: adding 64 (len 59 padlen 5 extra_pad 64) 
debug2: we sent a password packet, wait for reply 
debug1: Authentication succeeded (password). 
Authenticated to 123.123.123.123 ([123.123.123.123]:22). 
debug1: channel 0: new [client-session] 
debug3: ssh_session2_open: channel_new: 0 
debug2: channel 0: send open 
debug1: Entering interactive session. 
debug2: callback start 
debug2: client_session2_setup: id 0 
debug2: fd 3 setting TCP_NODELAY 
debug2: channel 0: request pty-req confirm 1 
debug1: Sending environment. 
debug3: Ignored env SSH_AGENT_PID 
debug3: Ignored env GPG_AGENT_INFO 
debug3: Ignored env TERM 
debug3: Ignored env SHELL 
debug3: Ignored env XDG_SESSION_COOKIE 
debug3: Ignored env WINDOWID 
debug3: Ignored env GNOME_KEYRING_CONTROL 
debug3: Ignored env USER 
debug3: Ignored env SSH_AUTH_SOCK 
debug3: Ignored env SESSION_MANAGER 
debug3: Ignored env USERNAME 
debug3: Ignored env DEFAULTS_PATH 
debug3: Ignored env XDG_CONFIG_DIRS 
debug3: Ignored env PATH 
debug3: Ignored env DESKTOP_SESSION 
debug3: Ignored env PWD 
debug1: Sending env LANG = en_US.UTF-8 
debug2: channel 0: request env confirm 0 
debug3: Ignored env MANDATORY_PATH 
debug3: Ignored env MDM_XSERVER_LOCATION 
debug3: Ignored env SHLVL 
debug3: Ignored env HOME 
debug3: Ignored env GNOME_DESKTOP_SESSION_ID 
debug3: Ignored env LOGNAME 
debug3: Ignored env XDG_DATA_DIRS 
debug3: Ignored env DBUS_SESSION_BUS_ADDRESS 
debug3: Ignored env MDMSESSION 
debug3: Ignored env WINDOWPATH 
debug3: Ignored env DISPLAY 
debug3: Ignored env MDM_LANG 
debug3: Ignored env XDG_CURRENT_DESKTOP 
debug3: Ignored env COLORTERM 
debug3: Ignored env XAUTHORITY 
debug3: Ignored env _ 
debug2: channel 0: request shell confirm 1 
debug2: callback done 
debug2: channel 0: open confirm rwindow 24576 rmax 32768 
debug2: channel_input_status_confirm: type 99 id 0 
debug2: PTY allocation request accepted on channel 0 
debug2: channel_input_status_confirm: type 99 id 0 
debug2: shell request accepted on channel 0 
login failed: please enter correct username and password 
Login: 

请您参考如下方法:

正如您在日志中看到的,即使是 ssh认为密码认证成功:

debug1: Authentication succeeded (password).



我相信发生的事情是:
  • 客户端( sshssh2_auth_password )发送密码
  • 服务器始终接受密码(根据 SSH 协议(protocol))
  • 但是当密码实际上错误时,服务器会打印错误

    login failed: please enter correct username and password



    并在终端上提示输入密码 (Login:)。它与例如命令提示符的消息和提示类型相同。 SSH 客户端不知道它与密码有关。它理所当然地认为身份验证成功并且正在进行正常的 shell session 。

  • 换句话说, ssh2_auth_password行为正确。是服务器实现不正确。


    评论关闭
    IT序号网

    微信公众号号:IT虾米 (左侧二维码扫一扫)欢迎添加!