3 .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
4 .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
5 .\" All rights reserved
7 .\" As far as I am concerned, the code I have written for this software
8 .\" can be used freely for any purpose. Any derived versions of this
9 .\" software must be clearly marked as such, and if the derived work is
10 .\" incompatible with the protocol description in the RFC file, it must be
11 .\" called by a name other than "ssh" or "Secure Shell".
13 .\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved.
14 .\" Copyright (c) 1999 Aaron Campbell. All rights reserved.
15 .\" Copyright (c) 1999 Theo de Raadt. All rights reserved.
17 .\" Redistribution and use in source and binary forms, with or without
18 .\" modification, are permitted provided that the following conditions
20 .\" 1. Redistributions of source code must retain the above copyright
21 .\" notice, this list of conditions and the following disclaimer.
22 .\" 2. Redistributions in binary form must reproduce the above copyright
23 .\" notice, this list of conditions and the following disclaimer in the
24 .\" documentation and/or other materials provided with the distribution.
26 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
27 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
28 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
29 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
30 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
31 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
32 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
33 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
34 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
35 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
37 .\" $OpenBSD: sshd_config.5,v 1.96 2008/07/02 02:24:18 djm Exp $
38 .Dd $Mdocdate: July 2 2008 $
43 .Nd OpenSSH SSH daemon configuration file
45 .Nm /etc/ssh/sshd_config
48 reads configuration data from
49 .Pa /etc/ssh/sshd_config
50 (or the file specified with
53 The file contains keyword-argument pairs, one per line.
56 and empty lines are interpreted as comments.
57 Arguments may optionally be enclosed in double quotes
59 in order to represent arguments containing spaces.
62 keywords and their meanings are as follows (note that
63 keywords are case-insensitive and arguments are case-sensitive):
66 Specifies what environment variables sent by the client will be copied into
73 for how to configure the client.
74 Note that environment passing is only supported for protocol 2.
75 Variables are specified by name, which may contain the wildcard characters
79 Multiple environment variables may be separated by whitespace or spread
83 Be warned that some environment variables could be used to bypass restricted
85 For this reason, care should be taken in the use of this directive.
86 The default is not to accept any environment variables.
88 Specifies which address family should be used by
98 .It Cm AllowAgentForwarding
101 forwarding is permitted.
104 Note that disabling agent forwarding does not improve security
105 unless users are also denied shell access, as they can always install
106 their own forwarders.
108 This keyword can be followed by a list of group name patterns, separated
110 If specified, login is allowed only for users whose primary
111 group or supplementary group list matches one of the patterns.
112 Only group names are valid; a numerical group ID is not recognized.
113 By default, login is allowed for all groups.
114 The allow/deny directives are processed in the following order:
125 for more information on patterns.
126 .It Cm AllowTcpForwarding
127 Specifies whether TCP forwarding is permitted.
130 Note that disabling TCP forwarding does not improve security unless
131 users are also denied shell access, as they can always install their
134 This keyword can be followed by a list of user name patterns, separated
136 If specified, login is allowed only for user names that
137 match one of the patterns.
138 Only user names are valid; a numerical user ID is not recognized.
139 By default, login is allowed for all users.
140 If the pattern takes the form USER@HOST then USER and HOST
141 are separately checked, restricting logins to particular
142 users from particular hosts.
143 The allow/deny directives are processed in the following order:
154 for more information on patterns.
155 .It Cm AuthorizedKeysFile
156 Specifies the file that contains the public keys that can be used
157 for user authentication.
158 .Cm AuthorizedKeysFile
159 may contain tokens of the form %T which are substituted during connection
161 The following tokens are defined: %% is replaced by a literal '%',
162 %h is replaced by the home directory of the user being authenticated, and
163 %u is replaced by the username of that user.
165 .Cm AuthorizedKeysFile
166 is taken to be an absolute path or one relative to the user's home
169 .Dq .ssh/authorized_keys .
171 The contents of the specified file are sent to the remote user before
172 authentication is allowed.
175 then no banner is displayed.
176 This option is only available for protocol version 2.
177 By default, no banner is displayed.
178 .It Cm ChallengeResponseAuthentication
179 Specifies whether challenge-response authentication is allowed.
182 this controls the use of PAM (see
185 Note that this affects the effectiveness of the
186 .Cm PasswordAuthentication
192 .It Cm ChrootDirectory
195 to after authentication.
196 This path, and all its components, must be root-owned directories that are
197 not writable by any other user or group.
199 The path may contain the following tokens that are expanded at runtime once
200 the connecting user has been authenticated: %% is replaced by a literal '%',
201 %h is replaced by the home directory of the user being authenticated, and
202 %u is replaced by the username of that user.
206 must contain the necessary files and directories to support the
208 For an interactive session this requires at least a shell, typically
222 For file transfer sessions using
224 no additional configuration of the environment is necessary if the
225 in-process sftp server is used (see
229 The default is not to
232 Specifies the ciphers allowed for protocol version 2.
233 Multiple ciphers must be comma-separated.
234 The supported ciphers are
249 .Bd -literal -offset 3n
250 aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,
251 arcfour256,arcfour,aes192-cbc,aes256-cbc,aes128-ctr,
252 aes192-ctr,aes256-ctr
254 .It Cm ClientAliveCountMax
255 Sets the number of client alive messages (see below) which may be
258 receiving any messages back from the client.
259 If this threshold is reached while client alive messages are being sent,
260 sshd will disconnect the client, terminating the session.
261 It is important to note that the use of client alive messages is very
265 The client alive messages are sent through the encrypted channel
266 and therefore will not be spoofable.
267 The TCP keepalive option enabled by
270 The client alive mechanism is valuable when the client or
271 server depend on knowing when a connection has become inactive.
273 The default value is 3.
275 .Cm ClientAliveInterval
276 (see below) is set to 15, and
277 .Cm ClientAliveCountMax
278 is left at the default, unresponsive SSH clients
279 will be disconnected after approximately 45 seconds.
280 This option applies to protocol version 2 only.
281 .It Cm ClientAliveInterval
282 Sets a timeout interval in seconds after which if no data has been received
285 will send a message through the encrypted
286 channel to request a response from the client.
288 is 0, indicating that these messages will not be sent to the client.
289 This option applies to protocol version 2 only.
291 Specifies whether compression is allowed, or delayed until
292 the user has authenticated successfully.
301 This keyword can be followed by a list of group name patterns, separated
303 Login is disallowed for users whose primary group or supplementary
304 group list matches one of the patterns.
305 Only group names are valid; a numerical group ID is not recognized.
306 By default, login is allowed for all groups.
307 The allow/deny directives are processed in the following order:
318 for more information on patterns.
320 This keyword can be followed by a list of user name patterns, separated
322 Login is disallowed for user names that match one of the patterns.
323 Only user names are valid; a numerical user ID is not recognized.
324 By default, login is allowed for all users.
325 If the pattern takes the form USER@HOST then USER and HOST
326 are separately checked, restricting logins to particular
327 users from particular hosts.
328 The allow/deny directives are processed in the following order:
339 for more information on patterns.
341 Forces the execution of the command specified by
343 ignoring any command supplied by the client and
346 The command is invoked by using the user's login shell with the -c option.
347 This applies to shell, command, or subsystem execution.
348 It is most useful inside a
351 The command originally supplied by the client is available in the
352 .Ev SSH_ORIGINAL_COMMAND
353 environment variable.
354 Specifying a command of
356 will force the use of an in-process sftp server that requires no support
358 .Cm ChrootDirectory .
360 Specifies whether remote hosts are allowed to connect to ports
361 forwarded for the client.
364 binds remote port forwardings to the loopback address.
365 This prevents other remote hosts from connecting to forwarded ports.
367 can be used to specify that sshd
368 should allow remote port forwardings to bind to non-loopback addresses, thus
369 allowing other hosts to connect.
372 to force remote port forwardings to be available to the local host only,
374 to force remote port forwardings to bind to the wildcard address, or
376 to allow the client to select the address to which the forwarding is bound.
379 .It Cm GSSAPIAuthentication
380 Specifies whether user authentication based on GSSAPI is allowed.
383 Note that this option applies to protocol version 2 only.
384 .It Cm GSSAPICleanupCredentials
385 Specifies whether to automatically destroy the user's credentials cache
389 Note that this option applies to protocol version 2 only.
390 .It Cm HostbasedAuthentication
391 Specifies whether rhosts or /etc/hosts.equiv authentication together
392 with successful public key client host authentication is allowed
393 (host-based authentication).
394 This option is similar to
395 .Cm RhostsRSAAuthentication
396 and applies to protocol version 2 only.
399 .It Cm HostbasedUsesNameFromPacketOnly
400 Specifies whether or not the server will attempt to perform a reverse
401 name lookup when matching the name in the
407 .Cm HostbasedAuthentication .
412 uses the name supplied by the client rather than
413 attempting to resolve the name from the TCP connection itself.
417 Specifies a file containing a private host key
420 .Pa /etc/ssh/ssh_host_key
421 for protocol version 1, and
422 .Pa /etc/ssh/ssh_host_rsa_key
424 .Pa /etc/ssh/ssh_host_dsa_key
425 for protocol version 2.
428 will refuse to use a file if it is group/world-accessible.
429 It is possible to have multiple host key files.
431 keys are used for version 1 and
435 are used for version 2 of the SSH protocol.
441 files will not be used in
442 .Cm RhostsRSAAuthentication
444 .Cm HostbasedAuthentication .
448 .Pa /etc/ssh/shosts.equiv
452 .It Cm IgnoreUserKnownHosts
455 should ignore the user's
456 .Pa ~/.ssh/known_hosts
458 .Cm RhostsRSAAuthentication
460 .Cm HostbasedAuthentication .
463 .It Cm KerberosAuthentication
464 Specifies whether the password provided by the user for
465 .Cm PasswordAuthentication
466 will be validated through the Kerberos KDC.
467 To use this option, the server needs a
468 Kerberos servtab which allows the verification of the KDC's identity.
471 .It Cm KerberosGetAFSToken
472 If AFS is active and the user has a Kerberos 5 TGT, attempt to acquire
473 an AFS token before accessing the user's home directory.
476 .It Cm KerberosOrLocalPasswd
477 If password authentication through Kerberos fails then
478 the password will be validated via any additional local mechanism
483 .It Cm KerberosTicketCleanup
484 Specifies whether to automatically destroy the user's ticket cache
488 .It Cm KeyRegenerationInterval
489 In protocol version 1, the ephemeral server key is automatically regenerated
490 after this many seconds (if it has been used).
491 The purpose of regeneration is to prevent
492 decrypting captured sessions by later breaking into the machine and
494 The key is never stored anywhere.
495 If the value is 0, the key is never regenerated.
496 The default is 3600 (seconds).
498 Specifies the local addresses
501 The following forms may be used:
503 .Bl -item -offset indent -compact
507 .Ar host No | Ar IPv4_addr No | Ar IPv6_addr
512 .Ar host No | Ar IPv4_addr No : Ar port
518 .Ar host No | Ar IPv6_addr Oc : Ar port
525 sshd will listen on the address and all prior
528 The default is to listen on all local addresses.
531 options are permitted.
534 options must precede this option for non-port qualified addresses.
535 .It Cm LoginGraceTime
536 The server disconnects after this time if the user has not
537 successfully logged in.
538 If the value is 0, there is no time limit.
539 The default is 120 seconds.
541 Gives the verbosity level that is used when logging messages from
543 The possible values are:
544 QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2, and DEBUG3.
546 DEBUG and DEBUG1 are equivalent.
547 DEBUG2 and DEBUG3 each specify higher levels of debugging output.
548 Logging with a DEBUG level violates the privacy of users and is not recommended.
550 Specifies the available MAC (message authentication code) algorithms.
551 The MAC algorithm is used in protocol version 2
552 for data integrity protection.
553 Multiple algorithms must be comma-separated.
555 .Bd -literal -offset indent
556 hmac-md5,hmac-sha1,umac-64@openssh.com,
557 hmac-ripemd160,hmac-sha1-96,hmac-md5-96
560 Introduces a conditional block.
561 If all of the criteria on the
563 line are satisfied, the keywords on the following lines override those
564 set in the global section of the config file, until either another
566 line or the end of the file.
570 are one or more criteria-pattern pairs.
571 The available criteria are
577 The match patterns may consist of single entries or comma-separated
578 lists and may use the wildcard and negation operators described in the
585 criteria may additionally contain addresses to match in CIDR
586 address/masklen format, e.g.\&
590 Note that the mask length provided must be consistent with the address -
591 it is an error to specify a mask length that is too long for the address
592 or one with bits set in this host portion of the address.
599 Only a subset of keywords may be used on the lines following a
602 Available keywords are
603 .Cm AllowTcpForwarding ,
605 .Cm ChrootDirectory ,
608 .Cm GSSAPIAuthentication ,
609 .Cm HostbasedAuthentication ,
610 .Cm KbdInteractiveAuthentication ,
611 .Cm KerberosAuthentication ,
614 .Cm PasswordAuthentication ,
616 .Cm PermitRootLogin ,
617 .Cm RhostsRSAAuthentication ,
618 .Cm RSAAuthentication ,
619 .Cm X11DisplayOffset ,
622 .Cm X11UseLocalHost .
624 Specifies the maximum number of authentication attempts permitted per
626 Once the number of failures reaches half this value,
627 additional failures are logged.
630 Specifies the maximum number of open sessions permitted per network connection.
633 Specifies the maximum number of concurrent unauthenticated connections to the
635 Additional connections will be dropped until authentication succeeds or the
637 expires for a connection.
640 Alternatively, random early drop can be enabled by specifying
641 the three colon separated values
645 will refuse connection attempts with a probability of
648 if there are currently
651 unauthenticated connections.
652 The probability increases linearly and all connection attempts
653 are refused if the number of unauthenticated connections reaches
656 .It Cm PasswordAuthentication
657 Specifies whether password authentication is allowed.
661 .Cm ChallengeResponseAuthentication
667 and the PAM authentication policy for
671 password authentication will be allowed through the challenge-response
672 mechanism regardless of the value of
673 .Cm PasswordAuthentication .
674 .It Cm PermitEmptyPasswords
675 When password authentication is allowed, it specifies whether the
676 server allows login to accounts with empty password strings.
680 Specifies the destinations to which TCP port forwarding is permitted.
681 The forwarding specification must be one of the following forms:
683 .Bl -item -offset indent -compact
697 .Ar \&[ IPv6_addr \&] : port
701 Multiple forwards may be specified by separating them with whitespace.
704 can be used to remove all restrictions and permit any forwarding requests.
705 By default all port forwarding requests are permitted.
706 .It Cm PermitRootLogin
707 Specifies whether root can log in using
711 .Dq without-password ,
712 .Dq forced-commands-only ,
718 .Cm ChallengeResponseAuthentication
721 the root user may be allowed in with its password even if
722 .Cm PermitRootLogin is set to
723 .Dq without-password .
725 If this option is set to
726 .Dq without-password ,
727 password authentication is disabled for root.
729 If this option is set to
730 .Dq forced-commands-only ,
731 root login with public key authentication will be allowed,
734 option has been specified
735 (which may be useful for taking remote backups even if root login is
736 normally not allowed).
737 All other authentication methods are disabled for root.
739 If this option is set to
741 root is not allowed to log in.
745 device forwarding is allowed.
761 .It Cm PermitUserEnvironment
763 .Pa ~/.ssh/environment
767 .Pa ~/.ssh/authorized_keys
772 Enabling environment processing may enable users to bypass access
773 restrictions in some configurations using mechanisms such as
776 Specifies the file that contains the process ID of the
779 .Pa /var/run/sshd.pid .
781 Specifies the port number that
785 Multiple options of this type are permitted.
791 should print the date and time of the last user login when a user logs
800 when a user logs in interactively.
801 (On some systems it is also printed by the shell,
807 Specifies the protocol versions
810 The possible values are
814 Multiple versions must be comma-separated.
817 Note that the order of the protocol list does not indicate preference,
818 because the client selects among multiple protocol versions offered
824 .It Cm PubkeyAuthentication
825 Specifies whether public key authentication is allowed.
828 Note that this option applies to protocol version 2 only.
829 .It Cm RhostsRSAAuthentication
830 Specifies whether rhosts or
832 authentication together
833 with successful RSA host authentication is allowed.
836 This option applies to protocol version 1 only.
837 .It Cm RSAAuthentication
838 Specifies whether pure RSA authentication is allowed.
841 This option applies to protocol version 1 only.
843 Defines the number of bits in the ephemeral protocol version 1 server key.
844 The minimum value is 512, and the default is 1024.
848 should check file modes and ownership of the
849 user's files and home directory before accepting login.
850 This is normally desirable because novices sometimes accidentally leave their
851 directory or files world-writable.
855 Configures an external subsystem (e.g. file transfer daemon).
856 Arguments should be a subsystem name and a command (with optional arguments)
857 to execute upon subsystem request.
863 file transfer subsystem.
867 implements an in-process
870 This may simplify configurations using
872 to force a different filesystem root on clients.
874 By default no subsystems are defined.
875 Note that this option applies to protocol version 2 only.
876 .It Cm SyslogFacility
877 Gives the facility code that is used when logging messages from
879 The possible values are: DAEMON, USER, AUTH, LOCAL0, LOCAL1, LOCAL2,
880 LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7.
883 Specifies whether the system should send TCP keepalive messages to the
885 If they are sent, death of the connection or crash of one
886 of the machines will be properly noticed.
887 However, this means that
888 connections will die if the route is down temporarily, and some people
890 On the other hand, if TCP keepalives are not sent,
891 sessions may hang indefinitely on the server, leaving
893 users and consuming server resources.
897 (to send TCP keepalive messages), and the server will notice
898 if the network goes down or the client host crashes.
899 This avoids infinitely hanging sessions.
901 To disable TCP keepalive messages, the value should be set to
906 should look up the remote host name and check that
907 the resolved host name for the remote IP address maps back to the
908 very same IP address.
914 is used for interactive login sessions.
919 is never used for remote command execution.
920 Note also, that if this is enabled,
922 will be disabled because
924 does not know how to handle
928 .Cm UsePrivilegeSeparation
929 is specified, it will be disabled after authentication.
931 Enables the Pluggable Authentication Module interface.
934 this will enable PAM authentication using
935 .Cm ChallengeResponseAuthentication
937 .Cm PasswordAuthentication
938 in addition to PAM account and session module processing for all
939 authentication types.
941 Because PAM challenge-response authentication usually serves an equivalent
942 role to password authentication, you should disable either
943 .Cm PasswordAuthentication
945 .Cm ChallengeResponseAuthentication.
949 is enabled, you will not be able to run
954 .It Cm UsePrivilegeSeparation
957 separates privileges by creating an unprivileged child process
958 to deal with incoming network traffic.
959 After successful authentication, another process will be created that has
960 the privilege of the authenticated user.
961 The goal of privilege separation is to prevent privilege
962 escalation by containing any corruption within the unprivileged processes.
965 .It Cm VersionAddendum
966 Specifies a string to append to the regular version string to identify
967 OS- or site-specific modifications.
969 .Dq DragonFly-20080927 .
970 .It Cm X11DisplayOffset
971 Specifies the first display number available for
974 This prevents sshd from interfering with real X11 servers.
977 Specifies whether X11 forwarding is permitted.
985 When X11 forwarding is enabled, there may be additional exposure to
986 the server and to client displays if the
988 proxy display is configured to listen on the wildcard address (see
990 below), though this is not the default.
991 Additionally, the authentication spoofing and authentication data
992 verification and substitution occur on the client side.
993 The security risk of using X11 forwarding is that the client's X11
994 display server may be exposed to attack when the SSH client requests
995 forwarding (see the warnings for
999 A system administrator may have a stance in which they want to
1000 protect clients that may expose themselves to attack by unwittingly
1001 requesting X11 forwarding, which can warrant a
1005 Note that disabling X11 forwarding does not prevent users from
1006 forwarding X11 traffic, as users can always install their own forwarders.
1007 X11 forwarding is automatically disabled if
1010 .It Cm X11UseLocalhost
1013 should bind the X11 forwarding server to the loopback address or to
1014 the wildcard address.
1016 sshd binds the forwarding server to the loopback address and sets the
1017 hostname part of the
1019 environment variable to
1021 This prevents remote hosts from connecting to the proxy display.
1022 However, some older X11 clients may not function with this
1027 to specify that the forwarding server should be bound to the wildcard
1029 The argument must be
1035 .It Cm XAuthLocation
1036 Specifies the full pathname of the
1040 .Pa /usr/X11R6/bin/xauth .
1044 command-line arguments and configuration file options that specify time
1045 may be expressed using a sequence of the form:
1047 .Ar time Op Ar qualifier ,
1051 is a positive integer value and
1053 is one of the following:
1055 .Bl -tag -width Ds -compact -offset indent
1070 Each member of the sequence is added together to calculate
1071 the total time value.
1073 Time format examples:
1075 .Bl -tag -width Ds -compact -offset indent
1077 600 seconds (10 minutes)
1081 1 hour 30 minutes (90 minutes)
1085 .It Pa /etc/ssh/sshd_config
1086 Contains configuration data for
1088 This file should be writable by root only, but it is recommended
1089 (though not necessary) that it be world-readable.
1094 OpenSSH is a derivative of the original and free
1095 ssh 1.2.12 release by Tatu Ylonen.
1096 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
1097 Theo de Raadt and Dug Song
1098 removed many bugs, re-added newer features and
1100 Markus Friedl contributed the support for SSH
1101 protocol versions 1.5 and 2.0.
1102 Niels Provos and Markus Friedl contributed support
1103 for privilege separation.
lentferj's projects / dragonfly.git / blob