☰

Windows 10 ssh禁用密码验证？

tag-icon • tag-icon ssh windows-10
Windows 10 ssh禁用密码验证？

Windows 10 最近添加了 OpenSSH 作为可选的 Windows 功能。我找到了配置文件 C:\Windows\System32\OpenSSH\sshd_config，并授予自己修改它的权限。

这是我拥有的文件：

#   $OpenBSD: sshd_config,v 1.84 2011/05/23 03:30:07 djm Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options override the
# default value.

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# The default requires explicit activation of protocol 1
#Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# 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

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#RSAAuthentication yes
#PubkeyAuthentication yes

# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
# but this is overridden so installations will only check .ssh/authorized_keys
AuthorizedKeysFile  .ssh/authorized_keys

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

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to no to disable s/key passwords
ChallengeResponseAuthentication no

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

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# 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

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
#ChrootDirectory none

# no default banner path
#Banner none

# override default of no subsystems
Subsystem   sftp    sftp-server.exe

# Example of overriding settings on a per-user basis
#Match User anoncvs
#   X11Forwarding no
#   AllowTcpForwarding no
#   ForceCommand cvs server
# PubkeyAcceptedKeyTypes ssh-ed25519*

ChallengeResponseAuthentication no
PasswordAuthentication no
UsePAM no

唯一非默认的条目是下面三行应该禁用密码验证。更改文件后，我转到服务并重新启动ssh-agent，，SSH Server Broke希望SSH Server Proxy他们能看到配置文件中的更改。然后我使用 putty ssh 到 localhost。Putty 要求输入我的用户名，然后要求输入我的密码，当我输入密码后，它成功连接。

在 Windows 10 的新 SSH 功能中，如何禁用密码验证？

答案1

在 Windows 10 v1803（又名 17134.191）中，它已经发生了变化。

编辑 c:\ProgramData\ssh\sshd_config (又名 %PROGRAMDATA%\ssh\sshd_config)

答案2

您注意到您有服务“SSH 服务器代理” - 此服务不是 Windows 10 Fall Creators Update (v1709) 中“OpenSSH 服务器（测试版）”可选功能的一部分。它是 Windows 开发人员模式的一部分 - 我想知道这是否（可能与 WSL 结合）导致您无意中连接到不同的 OpenSSH 服务器，以及为什么看起来配置没有被尊重。

尝试停止或禁用“SSH 服务器代理”服务并查看行为是否改变，或者，将 Windows\System32\OpenSSH\sshd_config 中的端口号调整为非标准端口并再次测试。

我刚刚部署了一个实验室 Windows 10 v1709 VM 来测试这一点，并且可以通过取消注释“# PasswordAuthentication yes”行（并将值切换为“no”）来确认，只需重新启动 sshd 服务，它就会阻止基于密码的登录。

“OpenSSH Server (beta)” 提供给我的唯一服务是“sshd”和“ssh-agent”。全新 VM，未启用 Windows 开发人员模式或 Ubuntu 上的 WSL/Bash。

相关内容