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.57 2006/03/14 16:32:48 markus Exp $
38 .Dd September 25, 1999
43 .Nd OpenSSH SSH daemon configuration file
45 .Bl -tag -width Ds -compact
46 .It Pa /etc/ssh/sshd_config
50 reads configuration data from
51 .Pa /etc/ssh/sshd_config
52 (or the file specified with
55 The file contains keyword-argument pairs, one per line.
58 and empty lines are interpreted as comments.
59 Arguments may optionally be enclosed in double quotes
61 in order to represent arguments containing spaces.
64 keywords and their meanings are as follows (note that
65 keywords are case-insensitive and arguments are case-sensitive):
68 Specifies what environment variables sent by the client will be copied into
75 for how to configure the client.
76 Note that environment passing is only supported for protocol 2.
77 Variables are specified by name, which may contain the wildcard characters
81 Multiple environment variables may be separated by whitespace or spread
85 Be warned that some environment variables could be used to bypass restricted
87 For this reason, care should be taken in the use of this directive.
88 The default is not to accept any environment variables.
90 Specifies which address family should be used by
101 This keyword can be followed by a list of group name patterns, separated
103 If specified, login is allowed only for users whose primary
104 group or supplementary group list matches one of the patterns.
105 Only group names are valid; a numerical group ID is not recognized.
106 By default, login is allowed for all groups.
107 The allow/deny directives are processed in the following order:
118 for more information on patterns.
119 .It Cm AllowTcpForwarding
120 Specifies whether TCP forwarding is permitted.
123 Note that disabling TCP forwarding does not improve security unless
124 users are also denied shell access, as they can always install their
127 This keyword can be followed by a list of user name patterns, separated
129 If specified, login is allowed only for user names that
130 match one of the patterns.
131 Only user names are valid; a numerical user ID is not recognized.
132 By default, login is allowed for all users.
133 If the pattern takes the form USER@HOST then USER and HOST
134 are separately checked, restricting logins to particular
135 users from particular hosts.
136 The allow/deny directives are processed in the following order:
147 for more information on patterns.
148 .It Cm AuthorizedKeysFile
149 Specifies the file that contains the public keys that can be used
150 for user authentication.
151 .Cm AuthorizedKeysFile
152 may contain tokens of the form %T which are substituted during connection
154 The following tokens are defined: %% is replaced by a literal '%',
155 %h is replaced by the home directory of the user being authenticated, and
156 %u is replaced by the username of that user.
158 .Cm AuthorizedKeysFile
159 is taken to be an absolute path or one relative to the user's home
162 .Dq .ssh/authorized_keys .
164 In some jurisdictions, sending a warning message before authentication
165 may be relevant for getting legal protection.
166 The contents of the specified file are sent to the remote user before
167 authentication is allowed.
168 This option is only available for protocol version 2.
169 By default, no banner is displayed.
170 .It Cm ChallengeResponseAuthentication
171 Specifies whether challenge-response authentication is allowed.
172 All authentication styles from
178 Specifies the ciphers allowed for protocol version 2.
179 Multiple ciphers must be comma-separated.
180 The supported ciphers are
195 .Bd -literal -offset 3n
196 aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,
197 arcfour256,arcfour,aes192-cbc,aes256-cbc,aes128-ctr,
198 aes192-ctr,aes256-ctr
200 .It Cm ClientAliveCountMax
201 Sets the number of client alive messages (see below) which may be
204 receiving any messages back from the client.
205 If this threshold is reached while client alive messages are being sent,
206 sshd will disconnect the client, terminating the session.
207 It is important to note that the use of client alive messages is very
211 The client alive messages are sent through the encrypted channel
212 and therefore will not be spoofable.
213 The TCP keepalive option enabled by
216 The client alive mechanism is valuable when the client or
217 server depend on knowing when a connection has become inactive.
219 The default value is 3.
221 .Cm ClientAliveInterval
222 (see below) is set to 15, and
223 .Cm ClientAliveCountMax
224 is left at the default, unresponsive SSH clients
225 will be disconnected after approximately 45 seconds.
226 This option applies to protocol version 2 only.
227 .It Cm ClientAliveInterval
228 Sets a timeout interval in seconds after which if no data has been received
231 will send a message through the encrypted
232 channel to request a response from the client.
234 is 0, indicating that these messages will not be sent to the client.
235 This option applies to protocol version 2 only.
237 Specifies whether compression is allowed, or delayed until
238 the user has authenticated successfully.
247 This keyword can be followed by a list of group name patterns, separated
249 Login is disallowed for users whose primary group or supplementary
250 group list matches one of the patterns.
251 Only group names are valid; a numerical group ID is not recognized.
252 By default, login is allowed for all groups.
253 The allow/deny directives are processed in the following order:
264 for more information on patterns.
266 This keyword can be followed by a list of user name patterns, separated
268 Login is disallowed for user names that match one of the patterns.
269 Only user names are valid; a numerical user ID is not recognized.
270 By default, login is allowed for all users.
271 If the pattern takes the form USER@HOST then USER and HOST
272 are separately checked, restricting logins to particular
273 users from particular hosts.
274 The allow/deny directives are processed in the following order:
285 for more information on patterns.
287 Specifies whether remote hosts are allowed to connect to ports
288 forwarded for the client.
291 binds remote port forwardings to the loopback address.
292 This prevents other remote hosts from connecting to forwarded ports.
294 can be used to specify that sshd
295 should allow remote port forwardings to bind to non-loopback addresses, thus
296 allowing other hosts to connect.
299 to force remote port forwardings to be available to the local host only,
301 to force remote port forwardings to bind to the wildcard address, or
303 to allow the client to select the address to which the forwarding is bound.
306 .It Cm GSSAPIAuthentication
307 Specifies whether user authentication based on GSSAPI is allowed.
310 Note that this option applies to protocol version 2 only.
311 .It Cm GSSAPICleanupCredentials
312 Specifies whether to automatically destroy the user's credentials cache
316 Note that this option applies to protocol version 2 only.
317 .It Cm HostbasedAuthentication
318 Specifies whether rhosts or /etc/hosts.equiv authentication together
319 with successful public key client host authentication is allowed
320 (host-based authentication).
321 This option is similar to
322 .Cm RhostsRSAAuthentication
323 and applies to protocol version 2 only.
327 Specifies a file containing a private host key
330 .Pa /etc/ssh/ssh_host_key
331 for protocol version 1, and
332 .Pa /etc/ssh/ssh_host_rsa_key
334 .Pa /etc/ssh/ssh_host_dsa_key
335 for protocol version 2.
338 will refuse to use a file if it is group/world-accessible.
339 It is possible to have multiple host key files.
341 keys are used for version 1 and
345 are used for version 2 of the SSH protocol.
351 files will not be used in
352 .Cm RhostsRSAAuthentication
354 .Cm HostbasedAuthentication .
358 .Pa /etc/shosts.equiv
362 .It Cm IgnoreUserKnownHosts
365 should ignore the user's
366 .Pa ~/.ssh/known_hosts
368 .Cm RhostsRSAAuthentication
370 .Cm HostbasedAuthentication .
373 .It Cm KerberosAuthentication
374 Specifies whether the password provided by the user for
375 .Cm PasswordAuthentication
376 will be validated through the Kerberos KDC.
377 To use this option, the server needs a
378 Kerberos servtab which allows the verification of the KDC's identity.
381 .It Cm KerberosGetAFSToken
382 If AFS is active and the user has a Kerberos 5 TGT, attempt to acquire
383 an AFS token before accessing the user's home directory.
386 .It Cm KerberosOrLocalPasswd
387 If password authentication through Kerberos fails then
388 the password will be validated via any additional local mechanism
393 .It Cm KerberosTicketCleanup
394 Specifies whether to automatically destroy the user's ticket cache
398 .It Cm KeyRegenerationInterval
399 In protocol version 1, the ephemeral server key is automatically regenerated
400 after this many seconds (if it has been used).
401 The purpose of regeneration is to prevent
402 decrypting captured sessions by later breaking into the machine and
404 The key is never stored anywhere.
405 If the value is 0, the key is never regenerated.
406 The default is 3600 (seconds).
408 Specifies the local addresses
411 The following forms may be used:
413 .Bl -item -offset indent -compact
417 .Ar host No | Ar IPv4_addr No | Ar IPv6_addr
422 .Ar host No | Ar IPv4_addr No : Ar port
428 .Ar host No | Ar IPv6_addr Oc : Ar port
435 sshd will listen on the address and all prior
438 The default is to listen on all local addresses.
441 options are permitted.
444 options must precede this option for non-port qualified addresses.
445 .It Cm LoginGraceTime
446 The server disconnects after this time if the user has not
447 successfully logged in.
448 If the value is 0, there is no time limit.
449 The default is 120 seconds.
451 Gives the verbosity level that is used when logging messages from
453 The possible values are:
454 QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2, and DEBUG3.
456 DEBUG and DEBUG1 are equivalent.
457 DEBUG2 and DEBUG3 each specify higher levels of debugging output.
458 Logging with a DEBUG level violates the privacy of users and is not recommended.
460 Specifies the available MAC (message authentication code) algorithms.
461 The MAC algorithm is used in protocol version 2
462 for data integrity protection.
463 Multiple algorithms must be comma-separated.
465 .Dq hmac-md5,hmac-sha1,hmac-ripemd160,hmac-sha1-96,hmac-md5-96 .
467 Specifies the maximum number of authentication attempts permitted per
469 Once the number of failures reaches half this value,
470 additional failures are logged.
473 Specifies the maximum number of concurrent unauthenticated connections to the
475 Additional connections will be dropped until authentication succeeds or the
477 expires for a connection.
480 Alternatively, random early drop can be enabled by specifying
481 the three colon separated values
485 will refuse connection attempts with a probability of
488 if there are currently
491 unauthenticated connections.
492 The probability increases linearly and all connection attempts
493 are refused if the number of unauthenticated connections reaches
496 .It Cm PasswordAuthentication
497 Specifies whether password authentication is allowed.
500 .It Cm PermitEmptyPasswords
501 When password authentication is allowed, it specifies whether the
502 server allows login to accounts with empty password strings.
505 .It Cm PermitRootLogin
506 Specifies whether root can log in using
510 .Dq without-password ,
511 .Dq forced-commands-only ,
517 If this option is set to
518 .Dq without-password ,
519 password authentication is disabled for root.
521 If this option is set to
522 .Dq forced-commands-only ,
523 root login with public key authentication will be allowed,
526 option has been specified
527 (which may be useful for taking remote backups even if root login is
528 normally not allowed).
529 All other authentication methods are disabled for root.
531 If this option is set to
533 root is not allowed to log in.
537 device forwarding is allowed.
546 .It Cm PermitUserEnvironment
548 .Pa ~/.ssh/environment
552 .Pa ~/.ssh/authorized_keys
557 Enabling environment processing may enable users to bypass access
558 restrictions in some configurations using mechanisms such as
561 Specifies the file that contains the process ID of the
564 .Pa /var/run/sshd.pid .
566 Specifies the port number that
570 Multiple options of this type are permitted.
576 should print the date and time of the last user login when a user logs
585 when a user logs in interactively.
586 (On some systems it is also printed by the shell,
592 Specifies the protocol versions
595 The possible values are
599 Multiple versions must be comma-separated.
602 Note that the order of the protocol list does not indicate preference,
603 because the client selects among multiple protocol versions offered
609 .It Cm PubkeyAuthentication
610 Specifies whether public key authentication is allowed.
613 Note that this option applies to protocol version 2 only.
614 .It Cm RhostsRSAAuthentication
615 Specifies whether rhosts or /etc/hosts.equiv authentication together
616 with successful RSA host authentication is allowed.
619 This option applies to protocol version 1 only.
620 .It Cm RSAAuthentication
621 Specifies whether pure RSA authentication is allowed.
624 This option applies to protocol version 1 only.
626 Defines the number of bits in the ephemeral protocol version 1 server key.
627 The minimum value is 512, and the default is 768.
631 should check file modes and ownership of the
632 user's files and home directory before accepting login.
633 This is normally desirable because novices sometimes accidentally leave their
634 directory or files world-writable.
638 Configures an external subsystem (e.g. file transfer daemon).
639 Arguments should be a subsystem name and a command to execute upon subsystem
645 file transfer subsystem.
646 By default no subsystems are defined.
647 Note that this option applies to protocol version 2 only.
648 .It Cm SyslogFacility
649 Gives the facility code that is used when logging messages from
651 The possible values are: DAEMON, USER, AUTH, LOCAL0, LOCAL1, LOCAL2,
652 LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7.
655 Specifies whether the system should send TCP keepalive messages to the
657 If they are sent, death of the connection or crash of one
658 of the machines will be properly noticed.
659 However, this means that
660 connections will die if the route is down temporarily, and some people
662 On the other hand, if TCP keepalives are not sent,
663 sessions may hang indefinitely on the server, leaving
665 users and consuming server resources.
669 (to send TCP keepalive messages), and the server will notice
670 if the network goes down or the client host crashes.
671 This avoids infinitely hanging sessions.
673 To disable TCP keepalive messages, the value should be set to
678 should look up the remote host name and check that
679 the resolved host name for the remote IP address maps back to the
680 very same IP address.
686 is used for interactive login sessions.
691 is never used for remote command execution.
692 Note also, that if this is enabled,
694 will be disabled because
696 does not know how to handle
700 .Cm UsePrivilegeSeparation
701 is specified, it will be disabled after authentication.
703 Enables the Pluggable Authentication Module interface.
706 this will enable PAM authentication using
707 .Cm ChallengeResponseAuthentication
709 .Cm PasswordAuthentication
710 in addition to PAM account and session module processing for all
711 authentication types.
713 Because PAM challenge-response authentication usually serves an equivalent
714 role to password authentication, you should disable either
715 .Cm PasswordAuthentication
717 .Cm ChallengeResponseAuthentication.
721 is enabled, you will not be able to run
726 .It Cm UsePrivilegeSeparation
729 separates privileges by creating an unprivileged child process
730 to deal with incoming network traffic.
731 After successful authentication, another process will be created that has
732 the privilege of the authenticated user.
733 The goal of privilege separation is to prevent privilege
734 escalation by containing any corruption within the unprivileged processes.
737 .It Cm X11DisplayOffset
738 Specifies the first display number available for
741 This prevents sshd from interfering with real X11 servers.
744 Specifies whether X11 forwarding is permitted.
752 When X11 forwarding is enabled, there may be additional exposure to
753 the server and to client displays if the
755 proxy display is configured to listen on the wildcard address (see
757 below), though this is not the default.
758 Additionally, the authentication spoofing and authentication data
759 verification and substitution occur on the client side.
760 The security risk of using X11 forwarding is that the client's X11
761 display server may be exposed to attack when the SSH client requests
762 forwarding (see the warnings for
766 A system administrator may have a stance in which they want to
767 protect clients that may expose themselves to attack by unwittingly
768 requesting X11 forwarding, which can warrant a
772 Note that disabling X11 forwarding does not prevent users from
773 forwarding X11 traffic, as users can always install their own forwarders.
774 X11 forwarding is automatically disabled if
777 .It Cm X11UseLocalhost
780 should bind the X11 forwarding server to the loopback address or to
781 the wildcard address.
783 sshd binds the forwarding server to the loopback address and sets the
786 environment variable to
788 This prevents remote hosts from connecting to the proxy display.
789 However, some older X11 clients may not function with this
794 to specify that the forwarding server should be bound to the wildcard
803 Specifies the full pathname of the
807 .Pa /usr/X11R6/bin/xauth .
811 command-line arguments and configuration file options that specify time
812 may be expressed using a sequence of the form:
814 .Ar time Op Ar qualifier ,
818 is a positive integer value and
820 is one of the following:
822 .Bl -tag -width Ds -compact -offset indent
837 Each member of the sequence is added together to calculate
838 the total time value.
840 Time format examples:
842 .Bl -tag -width Ds -compact -offset indent
844 600 seconds (10 minutes)
848 1 hour 30 minutes (90 minutes)
852 .It Pa /etc/ssh/sshd_config
853 Contains configuration data for
855 This file should be writable by root only, but it is recommended
856 (though not necessary) that it be world-readable.
861 OpenSSH is a derivative of the original and free
862 ssh 1.2.12 release by Tatu Ylonen.
863 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
864 Theo de Raadt and Dug Song
865 removed many bugs, re-added newer features and
867 Markus Friedl contributed the support for SSH
868 protocol versions 1.5 and 2.0.
869 Niels Provos and Markus Friedl contributed support
870 for privilege separation.
andersk / openssh.git / blob