我刚刚将我的公钥上传到服务器,确保权限是正确的,当我尝试记录它时,只是拒绝它.
在sshd_config中启用loglevel DEBUG后,我得到:
Nov 22 06:53:36 host-1 sshd[8612]: debug1: Forked child 8617. Nov 22 06:53:36 host-1 sshd[8617]: Set /proc/self/oom_score_adj to 0 Nov 22 06:53:36 host-1 sshd[8617]: debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8 Nov 22 06:53:36 host-1 sshd[8617]: debug1: inetd sockets after dupping: 3,3 Nov 22 06:53:36 host-1 sshd[8617]: Connection from some_ip port 50466 Nov 22 06:53:36 host-1 sshd[8617]: debug1: HPN Disabled: 0,HPN Buffer Size: 87380 Nov 22 06:53:36 host-1 sshd[8617]: debug1: Client protocol version 2.0; client software version OpenSSH_6.0p1 Debian-3 Nov 22 06:53:36 host-1 sshd[8617]: SSH: Server;Ltype: Version;Remote: some_ip-50466;Protocol: 2.0;Client: OpenSSH_6.0p1 Debian-3 Nov 22 06:53:36 host-1 sshd[8617]: debug1: match: OpenSSH_6.0p1 Debian-3 pat OpenSSH* Nov 22 06:53:36 host-1 sshd[8617]: debug1: Remote is NON-HPN aware Nov 22 06:53:36 host-1 sshd[8617]: debug1: Enabling compatibility mode for protocol 2.0 Nov 22 06:53:36 host-1 sshd[8617]: debug1: Local version string SSH-2.0-OpenSSH_5.8p1-hpn13v10 Nov 22 06:53:36 host-1 sshd[8617]: debug1: Config token is loglevel Nov 22 06:53:36 host-1 sshd[8617]: debug1: Config token is passwordauthentication Nov 22 06:53:36 host-1 sshd[8617]: debug1: Config token is permitemptypasswords Nov 22 06:53:36 host-1 sshd[8617]: debug1: Config token is usepam Nov 22 06:53:36 host-1 sshd[8617]: debug1: Config token is subsystem Nov 22 06:53:36 host-1 sshd[8617]: debug1: temporarily_use_uid: 1000/1000 (e=0/0) Nov 22 06:53:36 host-1 sshd[8617]: debug1: trying public key file /home/xxx/.ssh/authorized_keys Nov 22 06:53:36 host-1 sshd[8617]: debug1: fd 4 clearing O_NONBLOCK Nov 22 06:53:36 host-1 sshd[8617]: debug1: restore_uid: 0/0 Nov 22 06:53:36 host-1 sshd[8617]: debug1: temporarily_use_uid: 1000/1000 (e=0/0) Nov 22 06:53:36 host-1 sshd[8617]: debug1: trying public key file /home/xxx/.ssh/authorized_keys2 Nov 22 06:53:36 host-1 sshd[8617]: debug1: Could not open authorized keys '/home/xxx/.ssh/authorized_keys2': No such file or directory Nov 22 06:53:36 host-1 sshd[8617]: debug1: restore_uid: 0/0 Nov 22 06:53:36 host-1 sshd[8617]: Failed publickey for xxx from some_ip port 50466 ssh2 Nov 22 06:53:36 host-1 sshd[8617]: debug1: temporarily_use_uid: 1000/1000 (e=0/0) Nov 22 06:53:36 host-1 sshd[8617]: debug1: trying public key file /home/xxx/.ssh/authorized_keys Nov 22 06:53:36 host-1 sshd[8617]: debug1: fd 4 clearing O_NONBLOCK Nov 22 06:53:36 host-1 sshd[8617]: debug1: restore_uid: 0/0 Nov 22 06:53:36 host-1 sshd[8617]: debug1: temporarily_use_uid: 1000/1000 (e=0/0) Nov 22 06:53:36 host-1 sshd[8617]: debug1: trying public key file /home/xxx/.ssh/authorized_keys2 Nov 22 06:53:36 host-1 sshd[8617]: debug1: Could not open authorized keys '/home/xxx/.ssh/authorized_keys2': No such file or directory Nov 22 06:53:36 host-1 sshd[8617]: debug1: restore_uid: 0/0 Nov 22 06:53:36 host-1 sshd[8617]: Failed publickey for xxx from some_ip port 50466 ssh2 Nov 22 06:53:36 host-1 sshd[8617]: debug1: do_cleanup
它继续尝试authorized_keys2(我虽然到处都弃用了)但是它确实在某个时候打开了authorized_keys(带有我的键的正确文件)然后再说完全没有关于它并返回到authorized_keys2
这有什么不对?
我的sshd_config中有:
PubkeyAuthentication yes AuthorizedKeysFile .ssh/authorized_keys
并且该文件中没有authorized_keys2字符串.是的,sshd在测试之前重新启动.
我想我可以使用authorized_keys2,但想了解这里发生了什么.有什么线索吗?
编辑:ssh -v host
client$ssh -v host OpenSSH_6.0p1 Debian-3,OpenSSL 1.0.1c 10 May 2012 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to host [someip] port 22. debug1: Connection established. debug1: identity file /home/xxx/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/xxx/.ssh/id_rsa-cert type -1 debug1: identity file /home/xxx/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/xxx/.ssh/id_dsa-cert type -1 debug1: identity file /home/xxx/.ssh/id_ecdsa type -1 debug1: identity file /home/xxx/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0,remote software version OpenSSH_5.8p1-hpn13v10 debug1: match: OpenSSH_5.8p1-hpn13v10 pat OpenSSH_5* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.0p1 Debian-3 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA xx:xx... debug1: Host 'host' is known and matches the ECDSA host key. debug1: Found key in /home/xxx/.ssh/known_hosts:11 debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: /home/xxx/.ssh/id_dsa debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Offering RSA public key: /home/xxx/.ssh/id_rsa debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Trying private key: /home/xxx/.ssh/id_ecdsa debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: password xxx@host's password:
解决方法
当它找不到有效的authorized_keys文件时,由于兼容性原因,它似乎回退到authorized_keys2.检查您的authorized_keys文件是否正确形成.