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: ssh_config.5,v 1.84 2006/02/24 23:20:07 jmc Exp $
38 .Dd September 25, 1999
43 .Nd OpenSSH SSH client configuration files
45 .Bl -tag -width Ds -compact
47 .It Pa /etc/ssh/ssh_config
51 obtains configuration data from the following sources in
54 .Bl -enum -offset indent -compact
58 user's configuration file
61 system-wide configuration file
62 .Pq Pa /etc/ssh/ssh_config
65 For each parameter, the first obtained value
67 The configuration files contain sections separated by
69 specifications, and that section is only applied for hosts that
70 match one of the patterns given in the specification.
71 The matched host name is the one given on the command line.
73 Since the first obtained value for each parameter is used, more
74 host-specific declarations should be given near the beginning of the
75 file, and general defaults at the end.
79 consists of zero or more non-whitespace characters,
81 (a wildcard that matches zero or more characters),
84 (a wildcard that matches exactly one character).
85 For example, to specify a set of declarations for any host in the
88 the following pattern could be used:
93 would match any host in the 192.168.0.[0-9] network range:
99 is a comma-separated list of patterns.
100 Patterns within pattern-lists may be negated
101 by preceding them with an exclamation mark
104 to allow a key to be used from anywhere within an organisation
108 the following entry (in authorized_keys) could be used:
110 .Dl from=\&"!*.dialup.example.com,*.example.com\&"
112 The configuration file has the following format:
114 Empty lines and lines starting with
117 Otherwise a line is of the format
118 .Dq keyword arguments .
119 Configuration options may be separated by whitespace or
120 optional whitespace and exactly one
122 the latter format is useful to avoid the need to quote whitespace
123 when specifying configuration options using the
132 keywords and their meanings are as follows (note that
133 keywords are case-insensitive and arguments are case-sensitive):
136 Restricts the following declarations (up to the next
138 keyword) to be only for those hosts that match one of the patterns
139 given after the keyword.
142 as a pattern can be used to provide global
143 defaults for all hosts.
146 argument given on the command line (i.e. the name is not converted to
147 a canonicalized host name before matching).
151 for more information on patterns.
153 Specifies which address family to use when connecting.
163 passphrase/password querying will be disabled.
164 This option is useful in scripts and other batch jobs where no user
165 is present to supply the password.
173 Use the specified address on the local machine as the source address of
175 Only useful on systems with more than one address.
176 Note that this option does not work if
177 .Cm UsePrivilegedPort
180 .It Cm ChallengeResponseAuthentication
181 Specifies whether to use challenge-response authentication.
182 The argument to this keyword must be
189 If this flag is set to
192 will additionally check the host IP address in the
195 This allows ssh to detect if a host key changed due to DNS spoofing.
196 If the option is set to
198 the check will not be executed.
202 Specifies the cipher to use for encrypting the session
203 in protocol version 1.
211 is only supported in the
213 client for interoperability with legacy protocol 1 implementations
214 that do not support the
217 Its use is strongly discouraged due to cryptographic weaknesses.
221 Specifies the ciphers allowed for protocol version 2
222 in order of preference.
223 Multiple ciphers must be comma-separated.
224 The supported ciphers are
239 .Bd -literal -offset 3n
240 aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,
241 arcfour256,arcfour,aes192-cbc,aes256-cbc,aes128-ctr,
242 aes192-ctr,aes256-ctr
244 .It Cm ClearAllForwardings
245 Specifies that all local, remote, and dynamic port forwardings
246 specified in the configuration files or on the command line be
248 This option is primarily useful when used from the
250 command line to clear port forwardings set in
251 configuration files, and is automatically set by
262 Specifies whether to use compression.
269 .It Cm CompressionLevel
270 Specifies the compression level to use if compression is enabled.
271 The argument must be an integer from 1 (fast) to 9 (slow, best).
272 The default level is 6, which is good for most applications.
273 The meaning of the values is the same as in
275 Note that this option applies to protocol version 1 only.
276 .It Cm ConnectionAttempts
277 Specifies the number of tries (one per second) to make before exiting.
278 The argument must be an integer.
279 This may be useful in scripts if the connection sometimes fails.
281 .It Cm ConnectTimeout
282 Specifies the timeout (in seconds) used when connecting to the
283 SSH server, instead of using the default system TCP timeout.
284 This value is used only when the target is down or really unreachable,
285 not when it refuses the connection.
287 Enables the sharing of multiple sessions over a single network connection.
291 will listen for connections on a control socket specified using the
294 Additional sessions can connect to this socket using the same
301 These sessions will try to reuse the master instance's network connection
302 rather than initiating new ones, but will fall back to connecting normally
303 if the control socket does not exist, or is not listening.
308 to listen for control connections, but require confirmation using the
310 program before they are accepted (see
316 ssh will continue without connecting to a master instance.
320 forwarding is supported over these multiplexed connections, however the
321 display and agent forwarded will be the one belonging to the master
322 connection i.e. it is not possible to forward multiple displays or agents.
324 Two additional options allow for opportunistic multiplexing: try to use a
325 master connection but fall back to creating a new one if one does not already
331 The latter requires confirmation like the
335 Specify the path to the control socket used for connection sharing as described
338 section above or the string
340 to disable connection sharing.
343 will be substituted by the local host name,
345 will be substituted by the target host name,
349 by the remote login username.
350 It is recommended that any
352 used for opportunistic connection sharing include
353 at least %h, %p, and %r.
354 This ensures that shared connections are uniquely identified.
355 .It Cm DynamicForward
356 Specifies that a TCP port on the local machine be forwarded
357 over the secure channel, and the application
358 protocol is then used to determine where to connect to from the
363 .Oo Ar bind_address : Oc Ar port .
365 IPv6 addresses can be specified by enclosing addresses in square brackets or
366 by using an alternative syntax:
367 .Oo Ar bind_address Ns / Oc Ns Ar port .
368 By default, the local port is bound in accordance with the
373 may be used to bind the connection to a specific address.
378 indicates that the listening port be bound for local use only, while an
381 indicates that the port should be available from all interfaces.
383 Currently the SOCKS4 and SOCKS5 protocols are supported, and
385 will act as a SOCKS server.
386 Multiple forwardings may be specified, and
387 additional forwardings can be given on the command line.
388 Only the superuser can forward privileged ports.
389 .It Cm EnableSSHKeysign
390 Setting this option to
392 in the global client configuration file
393 .Pa /etc/ssh/ssh_config
394 enables the use of the helper program
397 .Cm HostbasedAuthentication .
404 This option should be placed in the non-hostspecific section.
407 for more information.
409 Sets the escape character (default:
411 The escape character can also
412 be set on the command line.
413 The argument should be a single character,
415 followed by a letter, or
417 to disable the escape
418 character entirely (making the connection transparent for binary
421 Specifies whether the connection to the authentication agent (if any)
422 will be forwarded to the remote machine.
430 Agent forwarding should be enabled with caution.
431 Users with the ability to bypass file permissions on the remote host
432 (for the agent's Unix-domain socket)
433 can access the local agent through the forwarded connection.
434 An attacker cannot obtain key material from the agent,
435 however they can perform operations on the keys that enable them to
436 authenticate using the identities loaded into the agent.
438 Specifies whether X11 connections will be automatically redirected
439 over the secure channel and
449 X11 forwarding should be enabled with caution.
450 Users with the ability to bypass file permissions on the remote host
451 (for the user's X11 authorization database)
452 can access the local X11 display through the forwarded connection.
453 An attacker may then be able to perform activities such as keystroke monitoring
455 .Cm ForwardX11Trusted
456 option is also enabled.
457 .It Cm ForwardX11Trusted
458 If this option is set to
460 remote X11 clients will have full access to the original X11 display.
462 If this option is set to
464 remote X11 clients will be considered untrusted and prevented
465 from stealing or tampering with data belonging to trusted X11
469 token used for the session will be set to expire after 20 minutes.
470 Remote clients will be refused access after this time.
475 See the X11 SECURITY extension specification for full details on
476 the restrictions imposed on untrusted clients.
478 Specifies whether remote hosts are allowed to connect to local
482 binds local port forwardings to the loopback address.
483 This prevents other remote hosts from connecting to forwarded ports.
485 can be used to specify that ssh
486 should bind local port forwardings to the wildcard address,
487 thus allowing remote hosts to connect to forwarded ports.
494 .It Cm GlobalKnownHostsFile
495 Specifies a file to use for the global
496 host key database instead of
497 .Pa /etc/ssh/ssh_known_hosts .
498 .It Cm GSSAPIAuthentication
499 Specifies whether user authentication based on GSSAPI is allowed.
502 Note that this option applies to protocol version 2 only.
503 .It Cm GSSAPIDelegateCredentials
504 Forward (delegate) credentials to the server.
507 Note that this option applies to protocol version 2 only.
508 .It Cm HashKnownHosts
511 should hash host names and addresses when they are added to
512 .Pa ~/.ssh/known_hosts .
513 These hashed names may be used normally by
517 but they do not reveal identifying information should the file's contents
521 Note that hashing of names and addresses will not be retrospectively applied
522 to existing known hosts files, but these may be manually hashed using
524 .It Cm HostbasedAuthentication
525 Specifies whether to try rhosts based authentication with public key
533 This option applies to protocol version 2 only and
535 .Cm RhostsRSAAuthentication .
536 .It Cm HostKeyAlgorithms
537 Specifies the protocol version 2 host key algorithms
538 that the client wants to use in order of preference.
539 The default for this option is:
540 .Dq ssh-rsa,ssh-dss .
542 Specifies an alias that should be used instead of the
543 real host name when looking up or saving the host key
544 in the host key database files.
545 This option is useful for tunneling SSH connections
546 or for multiple servers running on a single host.
548 Specifies the real host name to log into.
549 This can be used to specify nicknames or abbreviations for hosts.
550 The default is the name given on the command line.
551 Numeric IP addresses are also permitted (both on the command line and in
554 .It Cm IdentitiesOnly
557 should only use the authentication identity files configured in the
562 offers more identities.
563 The argument to this keyword must be
567 This option is intended for situations where ssh-agent
568 offers many different identities.
572 Specifies a file from which the user's RSA or DSA authentication identity
576 for protocol version 1, and
580 for protocol version 2.
581 Additionally, any identities represented by the authentication agent
582 will be used for authentication.
583 The file name may use the tilde
584 syntax to refer to a user's home directory.
585 It is possible to have
586 multiple identity files specified in configuration files; all these
587 identities will be tried in sequence.
588 .It Cm KbdInteractiveDevices
589 Specifies the list of methods to use in keyboard-interactive authentication.
590 Multiple method names must be comma-separated.
591 The default is to use the server specified list.
593 Specifies a command to execute on the local machine after successfully
594 connecting to the server.
595 The command string extends to the end of the line, and is executed with
597 This directive is ignored unless
598 .Cm PermitLocalCommand
601 Specifies that a TCP port on the local machine be forwarded over
602 the secure channel to the specified host and port from the remote machine.
603 The first argument must be
605 .Oo Ar bind_address : Oc Ar port
607 and the second argument must be
608 .Ar host : Ns Ar hostport .
609 IPv6 addresses can be specified by enclosing addresses in square brackets or
610 by using an alternative syntax:
611 .Oo Ar bind_address Ns / Oc Ns Ar port
613 .Ar host Ns / Ns Ar hostport .
614 Multiple forwardings may be specified, and additional forwardings can be
615 given on the command line.
616 Only the superuser can forward privileged ports.
617 By default, the local port is bound in accordance with the
622 may be used to bind the connection to a specific address.
627 indicates that the listening port be bound for local use only, while an
630 indicates that the port should be available from all interfaces.
632 Gives the verbosity level that is used when logging messages from
634 The possible values are:
635 QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2, and DEBUG3.
637 DEBUG and DEBUG1 are equivalent.
638 DEBUG2 and DEBUG3 each specify higher levels of verbose output.
640 Specifies the MAC (message authentication code) algorithms
641 in order of preference.
642 The MAC algorithm is used in protocol version 2
643 for data integrity protection.
644 Multiple algorithms must be comma-separated.
646 .Dq hmac-md5,hmac-sha1,hmac-ripemd160,hmac-sha1-96,hmac-md5-96 .
647 .It Cm NoHostAuthenticationForLocalhost
648 This option can be used if the home directory is shared across machines.
649 In this case localhost will refer to a different machine on each of
650 the machines and the user will get many warnings about changed host keys.
651 However, this option disables host authentication for localhost.
652 The argument to this keyword must be
656 The default is to check the host key for localhost.
657 .It Cm NumberOfPasswordPrompts
658 Specifies the number of password prompts before giving up.
659 The argument to this keyword must be an integer.
661 .It Cm PasswordAuthentication
662 Specifies whether to use password authentication.
663 The argument to this keyword must be
669 .It Cm PermitLocalCommand
670 Allow local command execution via the
673 .Ic !\& Ns Ar command
683 Specifies the port number to connect on the remote host.
685 .It Cm PreferredAuthentications
686 Specifies the order in which the client should try protocol 2
687 authentication methods.
688 This allows a client to prefer one method (e.g.\&
689 .Cm keyboard-interactive )
690 over another method (e.g.\&
692 The default for this option is:
693 .Dq hostbased,publickey,keyboard-interactive,password .
695 Specifies the protocol versions
697 should support in order of preference.
698 The possible values are
702 Multiple versions must be comma-separated.
706 tries version 2 and falls back to version 1
707 if version 2 is not available.
709 Specifies the command to use to connect to the server.
711 string extends to the end of the line, and is executed with
713 In the command string,
715 will be substituted by the host name to
719 The command can be basically anything,
720 and should read from its standard input and write to its standard output.
721 It should eventually connect an
723 server running on some machine, or execute
726 Host key management will be done using the
727 HostName of the host being connected (defaulting to the name typed by
729 Setting the command to
731 disables this option entirely.
734 is not available for connects with a proxy command.
736 This directive is useful in conjunction with
738 and its proxy support.
739 For example, the following directive would connect via an HTTP proxy at
741 .Bd -literal -offset 3n
742 ProxyCommand /usr/bin/nc -X connect -x 192.0.2.0:8080 %h %p
744 .It Cm PubkeyAuthentication
745 Specifies whether to try public key authentication.
746 The argument to this keyword must be
752 This option applies to protocol version 2 only.
754 Specifies the maximum amount of data that may be transmitted before the
755 session key is renegotiated.
756 The argument is the number of bytes, with an optional suffix of
761 to indicate Kilobytes, Megabytes, or Gigabytes, respectively.
762 The default is between
766 depending on the cipher.
767 This option applies to protocol version 2 only.
769 Specifies that a TCP port on the remote machine be forwarded over
770 the secure channel to the specified host and port from the local machine.
771 The first argument must be
773 .Oo Ar bind_address : Oc Ar port
775 and the second argument must be
776 .Ar host : Ns Ar hostport .
777 IPv6 addresses can be specified by enclosing addresses in square brackets
778 or by using an alternative syntax:
779 .Oo Ar bind_address Ns / Oc Ns Ar port
781 .Ar host Ns / Ns Ar hostport .
782 Multiple forwardings may be specified, and additional
783 forwardings can be given on the command line.
784 Only the superuser can forward privileged ports.
788 is not specified, the default is to only bind to loopback addresses.
793 or an empty string, then the forwarding is requested to listen on all
797 will only succeed if the server's
799 option is enabled (see
800 .Xr sshd_config 5 ) .
801 .It Cm RhostsRSAAuthentication
802 Specifies whether to try rhosts based authentication with RSA host
810 This option applies to protocol version 1 only and requires
813 .It Cm RSAAuthentication
814 Specifies whether to try RSA authentication.
815 The argument to this keyword must be
819 RSA authentication will only be
820 attempted if the identity file exists, or an authentication agent is
824 Note that this option applies to protocol version 1 only.
826 Specifies what variables from the local
828 should be sent to the server.
829 Note that environment passing is only supported for protocol 2.
830 The server must also support it, and the server must be configured to
831 accept these environment variables.
836 for how to configure the server.
837 Variables are specified by name, which may contain wildcard characters.
838 Multiple environment variables may be separated by whitespace or spread
842 The default is not to send any environment variables.
846 for more information on patterns.
847 .It Cm ServerAliveCountMax
848 Sets the number of server alive messages (see below) which may be
851 receiving any messages back from the server.
852 If this threshold is reached while server alive messages are being sent,
853 ssh will disconnect from the server, terminating the session.
854 It is important to note that the use of server alive messages is very
858 The server alive messages are sent through the encrypted channel
859 and therefore will not be spoofable.
860 The TCP keepalive option enabled by
863 The server alive mechanism is valuable when the client or
864 server depend on knowing when a connection has become inactive.
866 The default value is 3.
868 .Cm ServerAliveInterval
869 (see below) is set to 15 and
870 .Cm ServerAliveCountMax
871 is left at the default, if the server becomes unresponsive,
872 ssh will disconnect after approximately 45 seconds.
873 .It Cm ServerAliveInterval
874 Sets a timeout interval in seconds after which if no data has been received
877 will send a message through the encrypted
878 channel to request a response from the server.
880 is 0, indicating that these messages will not be sent to the server.
881 This option applies to protocol version 2 only.
882 .It Cm SmartcardDevice
883 Specifies which smartcard device to use.
884 The argument to this keyword is the device
886 should use to communicate with a smartcard used for storing the user's
888 By default, no device is specified and smartcard support is not activated.
889 .It Cm StrictHostKeyChecking
890 If this flag is set to
893 will never automatically add host keys to the
894 .Pa ~/.ssh/known_hosts
895 file, and refuses to connect to hosts whose host key has changed.
896 This provides maximum protection against trojan horse attacks,
897 though it can be annoying when the
898 .Pa /etc/ssh/ssh_known_hosts
899 file is poorly maintained or when connections to new hosts are
901 This option forces the user to manually
903 If this flag is set to
905 ssh will automatically add new host keys to the
906 user known hosts files.
907 If this flag is set to
910 will be added to the user known host files only after the user
911 has confirmed that is what they really want to do, and
912 ssh will refuse to connect to hosts whose host key has changed.
914 known hosts will be verified automatically in all cases.
923 Specifies whether the system should send TCP keepalive messages to the
925 If they are sent, death of the connection or crash of one
926 of the machines will be properly noticed.
927 However, this means that
928 connections will die if the route is down temporarily, and some people
933 (to send TCP keepalive messages), and the client will notice
934 if the network goes down or the remote host dies.
935 This is important in scripts, and many users want it too.
937 To disable TCP keepalive messages, the value should be set to
942 device forwarding between the client and the server.
943 This option also allows requesting layer 2 (ethernet)
944 instead of layer 3 (point-to-point) tunneling from the server.
956 device on the client.
957 Without this option, the next available device will be used.
958 .It Cm UsePrivilegedPort
959 Specifies whether to use a privileged port for outgoing connections.
970 Note that this option must be set to
973 .Cm RhostsRSAAuthentication
976 Specifies the user to log in as.
977 This can be useful when a different user name is used on different machines.
978 This saves the trouble of
979 having to remember to give the user name on the command line.
980 .It Cm UserKnownHostsFile
981 Specifies a file to use for the user
982 host key database instead of
983 .Pa ~/.ssh/known_hosts .
984 .It Cm VerifyHostKeyDNS
985 Specifies whether to verify the remote key using DNS and SSHFP resource
987 If this option is set to
989 the client will implicitly trust keys that match a secure fingerprint
991 Insecure fingerprints will be handled as if this option was set to
993 If this option is set to
995 information on fingerprint match will be displayed, but the user will still
996 need to confirm new host keys according to the
997 .Cm StrictHostKeyChecking
1006 Note that this option applies to protocol version 2 only.
1009 .Sx VERIFYING HOST KEYS
1012 .It Cm XAuthLocation
1013 Specifies the full pathname of the
1017 .Pa /usr/X11R6/bin/xauth .
1021 .It Pa ~/.ssh/config
1022 This is the per-user configuration file.
1023 The format of this file is described above.
1024 This file is used by the SSH client.
1025 Because of the potential for abuse, this file must have strict permissions:
1026 read/write for the user, and not accessible by others.
1027 .It Pa /etc/ssh/ssh_config
1028 Systemwide configuration file.
1029 This file provides defaults for those
1030 values that are not specified in the user's configuration file, and
1031 for those users who do not have a configuration file.
1032 This file must be world-readable.
1037 OpenSSH is a derivative of the original and free
1038 ssh 1.2.12 release by Tatu Ylonen.
1039 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
1040 Theo de Raadt and Dug Song
1041 removed many bugs, re-added newer features and
1043 Markus Friedl contributed the support for SSH
1044 protocol versions 1.5 and 2.0.
andersk / openssh.git / blob