The server may be configured to refuse public-key-based, password-less authentication. I do not know about Sun_SSH, but in OpenSSH (the most prevalent SSH implementation on Linux/*BSD systems) this is a matter of changing some settings in /etc/ssh/sshd_config (options RSAAuthentication for v1 protocol, PubkeyAuthentication for v2).
Maybe your user was locked on the unix box. If you usually login with your own account and then "be" the functional user, if that user has "password login" functionalities enabled but you are not using it, it may be locked (password expired for example). Howerver, even if it is locket it will not prevent you from sudo it with the "be" command, but it will definitly prevent any ssh login even if the keys are trusted.
发布评论
评论(5)
对我有用。
works for me.
确保您的主目录 (
/export/home/webdev1
) 也具有700
权限。Make sure your home directory(
/export/home/webdev1
) too has700
permission.服务器可以配置为拒绝基于公钥的无密码认证。我不知道 Sun_SSH,但在 OpenSSH(Linux/*BSD 系统上最流行的 SSH 实现)中,这是更改
/etc/ssh/sshd_config
中的一些设置的问题(选项v1 协议为 RSAAuthentication
,v2 协议为PubkeyAuthentication
)。The server may be configured to refuse public-key-based, password-less authentication. I do not know about Sun_SSH, but in OpenSSH (the most prevalent SSH implementation on Linux/*BSD systems) this is a matter of changing some settings in
/etc/ssh/sshd_config
(optionsRSAAuthentication
for v1 protocol,PubkeyAuthentication
for v2).尝试
chmod -R 600 ~/.ssh/
可能是组/全局读取权限导致了问题。
try just
chmod -R 600 ~/.ssh/
Maybe the group/global read permission is causing an issue.
也许您的用户被锁定在 unix 机器上。如果您通常使用自己的帐户登录,然后“成为”功能用户,如果该用户启用了“密码登录”功能但您没有使用它,则该用户可能会被锁定(例如密码过期)。
然而,即使它是 locket,它也不会阻止您使用“be”命令对其进行 sudo,但即使密钥是可信的,它也肯定会阻止任何 ssh 登录。
Maybe your user was locked on the unix box. If you usually login with your own account and then "be" the functional user, if that user has "password login" functionalities enabled but you are not using it, it may be locked (password expired for example).
Howerver, even if it is locket it will not prevent you from sudo it with the "be" command, but it will definitly prevent any ssh login even if the keys are trusted.