【问题标题】:Disable password authentication for SSH [closed]禁用 SSH 的密码验证 [关闭]
【发布时间】:2014-01-20 19:29:26
【问题描述】:

我正在寻找一种方法来禁止 SSH 客户端访问密码提示,如 here 所述。

我无法为 root 登录禁用 password: 提示。我已将sshd_config 文件更改为:

ChallengeResponseAuthentication no
PasswordAuthentication no
UsePAM no

并且还更改了权限chmod 700 ~/.sshchmod 600 ~/.ssh/authorized_keys。我错过了什么?这需要我有密码吗?

详细转储:

debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/user/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/user/.ssh/id_dsa
debug1: Trying private key: /home/user/.ssh/id_ecdsa
debug1: Next authentication method: password

文件 /etc/ssh/sshd_config:

# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 768

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin no
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile    %h/.ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM no

【问题讨论】:

  • ssh -v user@server 获取详细输出以帮助您进行故障排除。
  • ssh_configsshd_config 都有 PasswordAuthentication -- 保持敏锐!
  • 为什么关闭?

标签: ubuntu ssh


【解决方案1】:

在文件/etc/ssh/sshd_config

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication no

取消注释第二行,如果需要,将 yes 更改为 no。

然后运行

service ssh restart

【讨论】:

  • 许多指南建议在服务器上将 ChallengeResponseAuthentication、PasswordAuthentication、UsePAM 从 yes 更改为 no。在Debian/Ubuntu下测试成功。
  • 仅供参考,重启服务的 systemd 方式是:systemctl restart sshd 这是较新 Ubuntu 上的默认设置。
  • 如何在禁用密码验证的情况下向服务器添加新密钥?当然有一种方法可以做到这一点,而无需打开密码验证,每次有人想要添加密钥时......
  • @Matthew 也许用ssh-copy-id
  • @iamyojimbo 但您仍然需要授权密钥才能连接并使用该命令发送密钥。
【解决方案2】:

这是一个自动执行此操作的单行代码

sed -i -E 's/#?PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config

#? 是一个扩展的正则表达式,无论它是否被注释,它都匹配行。 -E 开关启用对 sed 的扩展正则表达式支持。

【讨论】:

    【解决方案3】:

    运行

    service ssh restart
    

    而不是

    /etc/init.d/ssh restart
    

    这可能有效。

    【讨论】:

    • 这对我有用;有什么想法为什么不使用 init.d 吗?
    • 取决于你的 linux 风格...在 gentoo 上它们都对我有用。
    【解决方案4】:

    我遵循了这些步骤(对于 Mac)。

    /etc/ssh/sshd_config

    #ChallengeResponseAuthentication yes
    #PasswordAuthentication yes
    

    ChallengeResponseAuthentication no
    PasswordAuthentication no
    

    现在生成 RSA 密钥:

    ssh-keygen -t rsa -P '' -f ~/.ssh/id_rsa
    

    (对我来说,RSA 密钥有效。DSA 密钥无效。)

    将在~/.ssh/id_rsa 中生成一个私钥以及~/.ssh/id_rsa.pub(公钥)。

    现在移动到 .ssh 文件夹:cd ~/.ssh

    输入rm -rf authorized_keys(有时多个键会导致错误)。

    输入vi authorized_keys

    输入:wq保存这个空文件

    输入cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

    重启 SSH:

    sudo launchctl stop com.openssh.sshd
    sudo launchctl start com.openssh.sshd
    

    【讨论】:

    • 不能用touch创建空文件authorized_keys吗?
    • @PeterMortensen 是的,你可以,但你为什么要这样做?
    • @Timo 因为按键次数更少
    • @jewbix.cube 之前不需要创建文件,它会自动创建。试试看。
    • @Timo 是的,你是对的,但不清楚你是从之前的评论中提出的。
    【解决方案5】:

    禁用SSH密码认证的单行:

    sed -i 's/PasswordAuthentication yes/PasswordAuthentication no/g' /etc/ssh/sshd_config && service ssh restart
    

    【讨论】:

    • 不要这样做。在许多情况下,这只会更改注释掉的行,没有任何效果。只需手动编辑文件。
    • 也许让它成为行首的正则表达式:sed -iE 's/^PasswordAuthentication yes/PasswordAuthentication no/g' /etc/ssh/sshd_config
    猜你喜欢
    • 2021-03-21
    • 2014-03-08
    • 1970-01-01
    • 2020-04-20
    • 2016-07-18
    • 2019-04-28
    • 2018-02-03
    • 1970-01-01
    • 2011-07-30
    相关资源
    最近更新 更多