2013-03-18 119 views
0

我試圖通過ssh訪問遠程服務器。我無法通過CLI中的ssh命令來完成,但是可以通過putty ssh訪問相同的憑據。密碼嘗試後ssh服務器關閉連接

我使用的是Ubuntu 12.04。 我無法訪問ssh服務器,所以我無法更改sshd配置文件。

從其他機器通過ssh CLI命令訪問ssh服務器是可能的,但是從我的mashine中這是行不通的。憑據是正確的,因爲我可以通過膩子進行連接,並且當我輸入密碼時,我不會收到來自服務器的任何消息。它只是關閉連接。

命令我使用通過在CLI ssh連接是:

ssh -vv [email protected] 

這是輸出:

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 somehost.com [53.52.81.241] port 22. 
debug1: Connection established. 
debug1: identity file /home/djuki/.ssh/id_rsa type -1 
debug1: identity file /home/djuki/.ssh/id_rsa-cert type -1 
debug1: identity file /home/djuki/.ssh/id_dsa type -1 
debug1: identity file /home/djuki/.ssh/id_dsa-cert type -1 
debug1: identity file /home/djuki/.ssh/id_ecdsa type -1 
debug1: identity file /home/djuki/.ssh/id_ecdsa-cert type -1 
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3 
debug1: match: OpenSSH_4.3 pat OpenSSH_4* 
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 
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: [email protected],ssh-rsa-cert-  [email protected],ssh-rsa,[email protected],[email protected],[email protected],[email protected],[email protected],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,[email protected] 
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,[email protected] 
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: none,[email protected],zlib 
debug2: kex_parse_kexinit: none,[email protected],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-group-exchange-sha1,diffie-hellman-group14- sha1,diffie-hellman-group1-sha1 
debug2: kex_parse_kexinit: ssh-rsa,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,[email protected] 
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,[email protected] 
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: none,[email protected] 
debug2: kex_parse_kexinit: none,[email protected] 
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 
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent 
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP 
debug2: dh_gen_key: priv key bits set: 125/256 
debug2: bits set: 514/1024 
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent 
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY 
debug1: Server host key: RSA e5:55:0d:1a:0e:2e:c5:03:db:05:c3:85:af:cf:bd:cd 
debug1: Host 'somehost.com' is known and matches the RSA host key. 
debug1: Found key in /home/djuki/.ssh/known_hosts:1 
debug2: bits set: 499/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/djuki/.ssh/id_rsa ((nil)) 
debug2: key: /home/djuki/.ssh/id_dsa ((nil)) 
debug2: key: /home/djuki/.ssh/id_ecdsa ((nil)) 
debug1: Authentications that can continue: publickey,gssapi-with-mic,password 
debug1: Next authentication method: gssapi-with-mic 
debug1: Unspecified GSS failure. Minor code may provide more information 
Credentials cache file '/tmp/krb5cc_1000' not found 

debug1: Unspecified GSS failure. Minor code may provide more information 
Credentials cache file '/tmp/krb5cc_1000' not found 

debug1: Unspecified GSS failure. Minor code may provide more information 


debug1: Unspecified GSS failure. Minor code may provide more information 
Credentials cache file '/tmp/krb5cc_1000' not found 

debug2: we did not send a packet, disable method 
debug1: Next authentication method: publickey 
debug1: Trying private key: /home/djuki/.ssh/id_rsa 
debug1: Trying private key: /home/djuki/.ssh/id_dsa 
debug1: Trying private key: /home/djuki/.ssh/id_ecdsa 
debug2: we did not send a packet, disable method 
debug1: Next authentication method: password 
[email protected]'s password: 
debug2: we sent a password packet, wait for reply 
Connection closed by 30.52.83.243 

回答

0

首先,你可以嘗試ssh -o GSSAPIAuthentication=no [email protected];它應該使Unspecified GSS failure消息消失。

然後,如果你能夠連接putty,你可以在調試模式下連接並運行sshd在更高的端口上(你不需要做root用戶,但是不需要防火牆阻塞所有的端口):

/usr/sbin/sshd -d -e -p1234 

,然後你可以嘗試在CLI與

ssh -p 1234 [email protected] 

連接,你會看到,在您的膩子會議,爲什麼服務器關閉連接的原因。

0

檢查/ etc/SSH/sshd_config中的下列情況之一,

  1. LoginGraceTime,並確保它被設置爲一個時間限制,你可以輸入你的密碼。否則,如果您的請求在時間範圍內未得到認證,它將關閉連接。 (例如:這會給你1分鐘的窗口,LoginGraceTime 60)
  2. 「UseDNS no」將確保sshd不會嘗試解析主機名。如果ssh客戶端計算機和服務器使用兩個不同的域名服務器,並且它們指向相同主機名的不同IP,則最終可能會將您鎖定。所以「UseDNS否」可以解決這些問題。
  3. 「PasswordAuthentication yes」將確保SSHd接受用戶輸入的密碼。

這就是我所遇到的這個問題。

相關問題