277e41829d
It seems that our nodepool is configured with the ecdsa and ed25519 host keys from the nodepool nodes, but not the rsa or dsa keys. This is a problem when we try to test our puppet SSH configuration in CI, because the puppet module removes the ability for the Zuul executor to reach the node and perform cleanup tasks after the tests have completed. This patch adds back the HostKey settings that the nodepool images started out with. This should not affect the puppetmaster's or a rooter's ability to log into production servers that are already using an rsa host key. Change-Id: I150b76a632398d0a6f00d5b98ad7277c62377601
96 lines
2.8 KiB
Plaintext
96 lines
2.8 KiB
Plaintext
# 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
|
|
HostKey /etc/ssh/ssh_host_ed25519_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 <%= @permit_root_login %>
|
|
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 <%= scope.lookupvar('::ssh::params::sftp_path') %>
|
|
|
|
# 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 yes
|
|
|
|
# allow ansible connections from puppetmaster host
|
|
Match <%= @trusted_ssh_type %> <%= @trusted_ssh_source %>
|
|
PermitRootLogin without-password
|
|
# allow ansible connections from localhost
|
|
Match host localhost
|
|
PermitRootLogin without-password
|