2017-12-22 10 views
0

パスワードなしのSSHを使用して、ユーザ名naveedと同様にrootとして仮想サーバにログインできます。そのために、私はリモートのsshディレクトリに秘密鍵と公開鍵を作成し、authorized_keysファイルに公開鍵を追加しました。 しかし、私はssh comquestをするときにパスワードを尋ねます。 Comquestは私のリモートサーバのホスト名です。以下はリモートサーバ上のSSHに関する奇妙な問題

は私の権限情報です:

[email protected]:~$ ls ~/.ssh 
authorized_keys known_hosts local local.pub 

以下
[email protected]:~$ stat -c "%a %n" ~/.ssh 
755 /home/naveed/.ssh 
[email protected]:~$ stat -c "%a %n" ~/.ssh/authorized_keys 
644 /home/naveed/.ssh/authorized_keys 

私は以下

[email protected]:/usr/local/hadoop$ ssh -vvv comquest 
OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g 1 Mar 2016 
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 19: Applying options for * 
debug2: resolving "comquest" port 22 
debug2: ssh_connect_direct: needpriv 0 
debug1: Connecting to comquest [173.82.212.48] port 22. 
debug1: Connection established. 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/naveed/.ssh/id_rsa type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/naveed/.ssh/id_rsa-cert type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/naveed/.ssh/id_dsa type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/naveed/.ssh/id_dsa-cert type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/naveed/.ssh/id_ecdsa type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/naveed/.ssh/id_ecdsa-cert type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/naveed/.ssh/id_ed25519 type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/naveed/.ssh/id_ed25519-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2 
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.2 
debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.2 pat OpenSSH* compat 0x04000000 
debug2: fd 3 setting O_NONBLOCK 
debug1: Authenticating to comquest:22 as 'naveed' 
debug3: hostkeys_foreach: reading file "/home/naveed/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/naveed/.ssh/known_hosts:2 
debug3: load_hostkeys: loaded 1 keys from comquest 
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],rsa-sha2-512,rsa-sha2-256,ssh-rsa 
debug3: send packet: type 20 
debug1: SSH2_MSG_KEXINIT sent 
debug3: receive packet: type 20 
debug1: SSH2_MSG_KEXINIT received 
debug2: local client KEXINIT proposal 
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c 
debug2: host key algorithms: [email protected],rsa-sha2-512,rsa-sha2-256,ssh-rsa,[email protected],[email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519 
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc 
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc 
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: compression ctos: none,[email protected],zlib 
debug2: compression stoc: none,[email protected],zlib 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal 
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1 
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256 
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected] 
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected] 
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: compression ctos: none,[email protected] 
debug2: compression stoc: none,[email protected] 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: [email protected] 
debug1: kex: host key algorithm: rsa-sha2-512 
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none 
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none 
debug3: send packet: type 30 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY 
debug3: receive packet: type 31 
debug1: Server host key: ssh-rsa SHA256:jad0RkXVMVxVyKD+9eY7abnSnUEz31nn+IMCfVUk7CA 
debug3: hostkeys_foreach: reading file "/home/naveed/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/naveed/.ssh/known_hosts:2 
debug3: load_hostkeys: loaded 1 keys from comquest 
debug3: hostkeys_foreach: reading file "/home/naveed/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/naveed/.ssh/known_hosts:3 
debug3: load_hostkeys: loaded 1 keys from 173.82.212.48 
debug1: Host 'comquest' is known and matches the RSA host key. 
debug1: Found key in /home/naveed/.ssh/known_hosts:2 
debug3: send packet: type 21 
debug2: set_newkeys: mode 1 
debug1: rekey after 134217728 blocks 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug3: receive packet: type 21 
debug2: set_newkeys: mode 0 
debug1: rekey after 134217728 blocks 
debug1: SSH2_MSG_NEWKEYS received 
debug2: key: /home/naveed/.ssh/id_rsa ((nil)) 
debug2: key: /home/naveed/.ssh/id_dsa ((nil)) 
debug2: key: /home/naveed/.ssh/id_ecdsa ((nil)) 
debug2: key: /home/naveed/.ssh/id_ed25519 ((nil)) 
debug3: send packet: type 5 
debug3: receive packet: type 7 
debug1: SSH2_MSG_EXT_INFO received 
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512> 
debug3: receive packet: type 6 
debug2: service_accept: ssh-userauth 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug3: send packet: type 50 
debug3: receive packet: type 53 
debug3: input_userauth_banner 
CloudCone LLC 
----------------------------------------------- 
KVM Cloud Server   Ubuntu 16.04.3 LTS 
----------------------------------------------- 
Service Status    status.cloudcone.com 
Client Area & Help Desk app.cloudcone.com 
FAQs and Documentation  help.cloudcone.com 

-- NOTICE --------------------------------------------------------------- 
This computer system is for authorized users only. Individuals using this          
system without authority or in excess of their authority are subject to          
having all their activities on this system monitored and recorded or           
examined by any authorized person, including law enforcement, as system          
personnel deem appropriate. In the course of monitoring individuals           
improperly using the system or in the course of system maintenance, the          
activities of authorized users may also be monitored and recorded. Any          
material so recorded may be disclosed as appropriate. Anyone using this          
system consents to these terms. 
debug3: receive packet: type 51 
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/naveed/.ssh/id_rsa 
debug3: no such identity: /home/naveed/.ssh/id_rsa: No such file or directory 
debug1: Trying private key: /home/naveed/.ssh/id_dsa 
debug3: no such identity: /home/naveed/.ssh/id_dsa: No such file or directory 
debug1: Trying private key: /home/naveed/.ssh/id_ecdsa 
debug3: no such identity: /home/naveed/.ssh/id_ecdsa: No such file or directory 
debug1: Trying private key: /home/naveed/.ssh/id_ed25519 
debug3: no such identity: /home/naveed/.ssh/id_ed25519: No such file or directory 
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 
[email protected]'s password: 

[email protected]:$ ssh -vvv comquestとなったエラーがあることは私のリモートの〜/ .sshフォルダの内容です

localおよびlocal.pubは[email protected]によって生成された鍵で、にアクセスします。。 local.pubがauthorized_keysに追加されます。

+0

ヒント: 'id_rsa:No such file or directory' ...このファイルが必要です。サーバ上にあなたのSSHキーペアを再生成 –

答えて

0

秘密鍵はlocalという名前のファイルにありますが、これはsshが検索する名前ではありません(デフォルト)。 ssh -vvvの出力では、id_rsaid_dsaなど、デフォルトのキーファイル名のみを検索していることがわかります。

(それがキーの種類に応じて、例えばid_rsaまたは何でも、)期待される命名規則に合わせてlocallocal.pubファイルの名前を変更、またはあなたのsshコマンドラインに-o IdentityFile=~/.ssh/localを追加してください。

+0

しかし、私は同様の方法で私のラップトップ上の秘密鍵で名前を付けましたが、リモートサーバには問題はありません。とにかく、私は 'local'キーを削除し、' id_rsa'という名前の新しいペアを作成しました。 – Naveed

+1

ラップトップに '〜/ .ssh/config'に' local'を探すよう指示する 'IdentityFile'オプションがあるかもしれません。しかし、通常、SSHキーファイルのデフォルトの命名規則に固執する方が簡単です。 – Wyzard