☰

SSH 无密码登录

tag-icon • tag-icon ssh solaris public-key rsa
SSH 无密码登录

我知道您可以使用 ssh-keygen 生成公钥/私钥对。然后，您可以在远程服务器上安装公钥。然后，您无需提供密码即可登录。我尚未成功设置基于密钥的身份验证。SSH 总是提示输入密码。

有人能帮助我理解调试信息吗？

服务器信息

服务器 A

-bash-3.00$ uname -a
SunOS cusd2 5.10 Generic_118833-33 sun4u sparc SUNW,UltraAX-i2

服务器 B

bash-2.05$ uname -a
SunOS apc_dev1db1 5.9 Generic_118558-27 sun4u sparc SUNW,Sun-Fire-V240

植物钥匙

我在服务器 A 上生成了密钥对，然后将公钥复制到服务器 B。然后我将其重命名为 authorized_keys。

使用调试信息登录

-bash-3.00$ ssh sybase@apc_dev1db1 -v  
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f   
debug1: Reading configuration data /etc/ssh/ssh_config   
debug1: Rhosts Authentication disabled, originating port will not be trusted.  
debug1: ssh_connect: needpriv 0  
debug1: Connecting to apc_dev1db1 [192.168.1.44] port 22.   
debug1: Connection established.    
debug1: identity file /export/home/attlmw1/.ssh/identity type -1  
debug1: identity file /export/home/attlmw1/.ssh/id_rsa type 1  
debug1: identity file /export/home/attlmw1/.ssh/id_dsa type -1   
debug1: Remote protocol version 2.0, remote software version Sun_SSH_1.1  
debug1: no match: Sun_SSH_1.1  
debug1: Enabling compatibility mode for protocol 2.0  
debug1: Local version string SSH-2.0-Sun_SSH_1.1  
debug1: Failed to acquire GSS-API credentials for any mechanisms (No credentials were supplied, or the credentials were unavailable or inaccessible  
Unknown code 0  
)  
debug1: SSH2_MSG_KEXINIT sent  
debug1: SSH2_MSG_KEXINIT received  
debug1: kex: server->client aes128-cbc hmac-md5 none  
debug1: kex: client->server aes128-cbc hmac-md5 none  
debug1: Peer sent proposed langtags, ctos: en-US,es,fr,hi-IN,ja-JP,ko,ko-KR,zh,zh-CN,zh-HK,zh-TW,en-CA,es-MX,fr-CA,ja,th,th-TH,i-default  
debug1: Peer sent proposed langtags, stoc: en-US,es,fr,hi-IN,ja-JP,ko,ko-KR,zh,zh-CN,zh-HK,zh-TW,en-CA,es-MX,fr-CA,ja,th,th-TH,i-default  
debug1: We proposed langtags, ctos: i-default  
debug1: We proposed langtags, stoc: i-default  
debug1: Negotiated lang: i-default  
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent  
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP  
debug1: Remote: Negotiated main locale: C  
debug1: Remote: Negotiated messages locale: C  
debug1: dh_gen_key: priv key bits set: 139/256  
debug1: bits set: 1592/3191  
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent  
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY  
debug1: Host 'apc_dev1db1' is known and matches the RSA host key.  
debug1: Found key in /export/home/attlmw1/.ssh/known_hosts:1  
debug1: bits set: 1595/3191  
debug1: ssh_rsa_verify: signature correct  
debug1: newkeys: mode 1  
debug1: SSH2_MSG_NEWKEYS sent  
debug1: expecting SSH2_MSG_NEWKEYS  
debug1: newkeys: mode 0  
debug1: SSH2_MSG_NEWKEYS received  
debug1: done: ssh_kex2.  
debug1: send SSH2_MSG_SERVICE_REQUEST  
debug1: got SSH2_MSG_SERVICE_ACCEPT  
debug1: Authentications that can continue: publickey,password,keyboard-interactive  
debug1: Next authentication method: publickey  
debug1: Trying private key: /export/home/attlmw1/.ssh/identity  
debug1: Trying public key: /export/home/attlmw1/.ssh/id_rsa  
debug1: Authentications that can continue: publickey,password,keyboard-interactive  
debug1: Trying private key: /export/home/attlmw1/.ssh/id_dsa  
debug1: Next authentication method: keyboard-interactive  
Password:

相关文件的权限

bash-2.05$ uname -a  
SunOS apc_dev1db1 5.9 Generic_118558-27 sun4u sparc SUNW,Sun-Fire-V240  
bash-2.05$ ls -ld .ssh/  
drwx------   2 sybase   sybase       512 Sep  6 13:16 .ssh/  
bash-2.05$  
bash-2.05$ ls -l .ssh/authorized_keys  
-rw-------   1 sybase   sybase       224 Sep  6 08:31 .ssh/authorized_keys  


-bash-3.00$ uname -a  
SunOS cusd2 5.10 Generic_118833-33 sun4u sparc SUNW,UltraAX-i2  
-bash-3.00$  
-bash-3.00$ ls -ld .ssh/  
drwx------   2 attlmw1  other        512 Sep  6 08:08 .ssh/  
-bash-3.00$ ls -l .ssh/  
total 6  
-rw-------   1 attlmw1  other        887 Sep  5 18:10 id_rsa  
-rw-r--r--   1 attlmw1  other        223 Sep  5 18:10 id_rsa.pub  
-rw-r--r--   1 attlmw1  other        234 Sep  6 08:08 known_hosts

答案1

确保：

  • 具有authorized_keys权限 600。
  • sybase的 $HOME 文件夹，具有$HOME/.ssh权限 700 并由 拥有sybase。

还要查看服务器 B 上的 sshd 日志，它会告诉您更多详细信息。

答案2

在 solaris 上，您应该将用户的主目录设置为 755，将 .ssh 目录设置为 755，并将 .ssh/authorized_keys 设置为 600。

答案3

问题出在authorized_keys文件上。
在植入公钥时，正确的操作是将公钥复制到远程服务器并将其添加到authorized_keys文件中。
但我所做的是复制内容并将其粘贴到authorized_keys文件中。在putty上，这将使原始内容发生变化。原始行只有一行。但我复制粘贴后变成了两行。

答案4

将来，您可能不想复制和粘贴密钥，而是想使用此命令：

ssh-copy-id

这不仅允许您将您的公钥目录复制到您的authorized_key并设置正确的权限。

相关内容