/etc/ssh/sshd_config에 일치하는 주소와 일치하는 사용자 지시문이 모두 있을 수는 없습니다.

/etc/ssh/sshd_config에 일치하는 주소와 일치하는 사용자 지시문이 모두 있을 수는 없습니다.

시스템은 Redhat 8입니다.

/etc/ssh/sshd_config 파일에서 다음 구성을 찾았습니다.

#       $OpenBSD: sshd_config,v 1.103 2018/04/09 20:41:22 tj Exp $

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

# This sshd was compiled with PATH=/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/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.

# If you want to change the port on a SELinux system, you have to tell
# SELinux about this change.
# semanage port -a -t ssh_port_t -p tcp #PORTNUMBER
#
#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key

# Ciphers and keying
#RekeyLimit default none

# This system is following system-wide crypto policy. The changes to
# crypto properties (Ciphers, MACs, ...) will not have any effect here.
# They will be overridden by command-line options passed to the server
# on command line.
# Please, check manual pages for update-crypto-policies(8) and sshd_config(5).

# Logging
#SyslogFacility AUTH
SyslogFacility AUTHPRIV
#LogLevel INFO

# Authentication:

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

#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

#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# 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
PasswordAuthentication yes

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

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

# GSSAPI options
GSSAPIAuthentication yes
GSSAPICleanupCredentials no
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no
#GSSAPIEnablek5users no

# 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'.
# WARNING: 'UsePAM no' is not supported in Fedora and may cause several
# problems.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes

# It is recommended to use pam_motd in /etc/pam.d/sshd instead of PrintMotd,
# as it is more configurable and versatile than the built-in version.
PrintMotd no

#PrintLastLog yes
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /var/run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none

# no default banner path
#Banner none

# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL LANGUAGE
AcceptEnv XMODIFIERS

# override default of no subsystems
Subsystem       sftp    /usr/libexec/openssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#       X11Forwarding no
#       AllowTcpForwarding no
#       PermitTTY no
#       ForceCommand cvs server
DenyUsers nonprivuser
#Allow Root Login via Key from pooler:
Match Address 192.168.1.67
PermitRootLogin without-password

여기서 일치 주소 지시문은 다른 부서의 누군가가 폴러의 IP가 키를 사용하여 루트로 인증할 수 있도록 하는 데 사용됩니다.

나중에 루트 또는 키를 통해 액세스해야 하는 다른 서브넷에서 내 IP 세트를 추가해야 했습니다.

"일치 주소" 뒤에 다음 줄을 추가했습니다.

Match User root
 AllowUsers [email protected] [email protected] [email protected] 
PermitRootLogin without-password

하지만 이제 필요한 컴퓨터는 연결할 수 있지만 Match Address위 명령의 폴러 192.168.1.67에는 연결할 수 없습니다.

모든 서버의 연결을 허용하기 위해 동료가 추가한 "일치 주소" 지시어를 주석 처리했습니다.

#Allow Root Login via Key from pooler:
#Match Address 192.168.1.67
#PermitRootLogin without-password

나는 그의 IP를 내 지시어에 다음과 같이 추가했습니다:

Match User root
 AllowUsers [email protected] [email protected] [email protected] [email protected] 
PermitRootLogin without-password

이것이 작동하는 동안 원래 의도한 대로 작동하지 않는 이유를 이해할 수 없습니다. 이렇게 하면 내 설정이 동료들과 분리되어 유지됩니다. 좋은 점입니다.

문서를 읽었으며 내가 이해한 바에 따르면 다른 키워드를 사용하는 Match 지시문이 작동해야 합니다. 또한 매개변수 목록에서 공백을 사용할 수 있는 이유를 이해할 수 없지만 공백을 쉼표로 바꾸면 작동하지 않습니다.

/etc/ssh/sshd_config의 "일치" 섹션에 있는 사람들은 다음과 같이 말했습니다.

Match

Introduces a conditional block. If all of the criteria on the Match line are satisfied, the keywords on the following lines override those set in the global section of the config file, until either another Match line or the end of the file.
If a keyword appears in multiple Match blocks that are satisfied, only the first instance of the keyword is applied.

The arguments to Match are one or more criteria-pattern pairs or the single token All which matches all criteria.
The available criteria are User, Group, Host, LocalAddress, LocalPort, RDomain, and Address (with RDomain representing the rdomain(4) on which the connection was received).

The match patterns may consist of single entries or comma-separated lists and may use the wildcard and negation operators described in the PATTERNS section of ssh_config(5).

노트:

/etc/ssh/sshd_config 파일을 수정한 후 sshd 서비스가 다시 시작되어 변경 사항이 적용됩니다.

# systemctl restart sshd.service

관련 정보