Last active
January 17, 2021 08:12
-
-
Save holly/0402c240e74c6c8db8ff8a54736b7871 to your computer and use it in GitHub Desktop.
sshd_config sample
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Port 9022 | |
#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 | |
KexAlgorithms curve25519-sha256@libssh.org,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256 | |
Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr | |
MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-128@openssh.com | |
HostKeyAlgorithms ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,ssh-rsa,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256 | |
# Ciphers and keying | |
#RekeyLimit default none | |
# Logging | |
#SyslogFacility AUTH | |
#LogLevel INFO | |
# Authentication: | |
#LoginGraceTime 2m | |
#PermitRootLogin prohibit-password | |
#StrictModes yes | |
#MaxAuthTries 6 | |
#MaxSessions 10 | |
LoginGraceTime 10 | |
MaxAuthTries 1 | |
PermitRootLogin no | |
AllowGroups wheel accounts | |
ClientAliveInterval 60 | |
ClientAliveCountMax 3 | |
PubkeyAuthentication yes | |
PasswordAuthentication no | |
PermitEmptyPasswords no | |
# Change to no to disable s/key passwords | |
ChallengeResponseAuthentication no | |
#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 | |
PasswordAuthentication no | |
PermitEmptyPasswords no | |
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 | |
#PermitTTY yes | |
PrintMotd no # pam does that | |
#PrintLastLog yes | |
#TCPKeepAlive yes | |
#PermitUserEnvironment no | |
#Compression delayed | |
#ClientAliveInterval 0 | |
#ClientAliveCountMax 3 | |
UseDNS no | |
#PidFile /run/sshd.pid | |
#MaxStartups 10:30:100 | |
#PermitTunnel no | |
#ChrootDirectory none | |
#VersionAddendum none | |
# no default banner path | |
#Banner none | |
# override default of no subsystems | |
Subsystem sftp /usr/lib/ssh/sftp-server | |
Include /etc/ssh/sshd_config.d/* | |
# Example of overriding settings on a per-user basis | |
#Match User anoncvs | |
# X11Forwarding no | |
# AllowTcpForwarding no | |
# PermitTTY no | |
# ForceCommand cvs server | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment