2016-08-25 174 views
0

我試圖按照this文章,但但我得到的錯誤,而試圖ssh到數據管理部服務器有什麼不對?(這個命令只是上面的Hadoop) 請幫我找出這個問題SSH權限被拒絕的錯誤

$ ssh -v [email protected] 

debug1: Reading configuration data /home/ubuntu/.ssh/config 
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 19: Applying options for * 
debug1: Connecting to ec2-xx-xx-xxx-xxx.us-xxxx-2.compute.amazonaws.com [xx-xx-xx-xx] port 22. 
debug1: Connection established. 
debug1: identity file /home/ubuntu/.ssh/id_rsa type 1 
debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1 
debug1: identity file /home/ubuntu/.ssh/id_dsa type -1 
debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1 
debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1 
debug1: identity file /home/ubuntu/.ssh/id_ecdsa-cert type -1 
debug1: identity file /home/ubuntu/.ssh/id_ed25519 type -1 
debug1: identity file /home/ubuntu/.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.7 
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 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 8c:b6:90:4a:5d:97:8c:47:e1:96:dd:42:82:4a:56:a5 
debug1: Host 'ec2-xx-xxx-xxx-xx.us-west-2.compute.amazonaws.com' is known and matches the ECDSA host key. 
debug1: Found key in /home/ubuntu/.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: SSH2_MSG_SERVICE_REQUEST sent 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug1: Authentications that can continue: publickey 
debug1: Next authentication method: publickey 
debug1: Offering RSA public key: /home/ubuntu/.ssh/id_rsa 
debug1: Authentications that can continue: publickey 
debug1: Trying private key: /home/ubuntu/.ssh/id_dsa 
debug1: Trying private key: /home/ubuntu/.ssh/id_ecdsa 
debug1: Trying private key: /home/ubuntu/.ssh/id_ed25519 
debug1: No more authentication methods to try. 
Permission denied (publickey). 

的.ssh文件內容:

-rw------- 1 ubuntu ubuntu 400 Aug 24 04:35 authorized_keys_bkp 
-rw-rw-r-- 1 ubuntu ubuntu 0 Aug 25 02:37 authorized_keys’ 
-rw-rw-r-- 1 ubuntu ubuntu 1692 Aug 25 02:39 AmitKeyPari_Oregon.pem 
drwxrwxr-x 2 ubuntu ubuntu 4096 Aug 25 02:39 config 
-rw-r--r-- 1 ubuntu ubuntu 405 Aug 25 02:40 id_rsa.pub 
-rw------- 1 ubuntu ubuntu 1766 Aug 25 02:40 id_rsa 
-rw------- 1 ubuntu ubuntu 805 Aug 25 02:40 authorized_keys 
-rw-r--r-- 1 ubuntu ubuntu 444 Aug 25 02:41 known_hosts 
+0

發佈目錄和文件權限'.ssh'目錄及其內容。 – iamauser

+0

嗨編輯了這個問題。 – Amit

回答

1

確保你的公鑰是在服務器端的授權密鑰列表。 (將其複製到服務器端.ssh/authorized_keys文件中)

+0

它似乎是在上面的錯誤消息中作爲mentioed。 debug1:主機'ec2-xx-xxx-xxx-xx.us-west-2.compute.amazonaws.com'是已知的並且與ECDSA主機密鑰匹配。 debug1:找到密鑰在/home/ubuntu/.ssh/known_hosts:3 – Amit

+0

不,這是機器的關鍵。它告訴你,對機器的加密不會受到中間人攻擊(或者至少從交換密鑰後它不是新的MITM攻擊)。你的公鑰是不同的;它是一個個人密鑰,而不是主機密鑰,當您嘗試登錄到服務器上的特定帳戶時,該密鑰會告知其他計算機信任您的私鑰。 – Tom

+0

@Amit我相信這只是表示它識別主機,因爲您之前已嘗試連接它,但這並不一定意味着您擁有有效的身份驗證密鑰 – Himself12794