2 .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
3 .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
4 .\" All rights reserved
6 .\" As far as I am concerned, the code I have written for this software
7 .\" can be used freely for any purpose. Any derived versions of this
8 .\" software must be clearly marked as such, and if the derived work is
9 .\" incompatible with the protocol description in the RFC file, it must be
10 .\" called by a name other than "ssh" or "Secure Shell".
12 .\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved.
13 .\" Copyright (c) 1999 Aaron Campbell. All rights reserved.
14 .\" Copyright (c) 1999 Theo de Raadt. All rights reserved.
16 .\" Redistribution and use in source and binary forms, with or without
17 .\" modification, are permitted provided that the following conditions
19 .\" 1. Redistributions of source code must retain the above copyright
20 .\" notice, this list of conditions and the following disclaimer.
21 .\" 2. Redistributions in binary form must reproduce the above copyright
22 .\" notice, this list of conditions and the following disclaimer in the
23 .\" documentation and/or other materials provided with the distribution.
25 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
26 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
27 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
28 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
29 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
30 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
31 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
32 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
33 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
34 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
36 .\" $OpenBSD: ssh_config.5,v 1.161 2013/01/08 18:49:04 markus Exp $
43 .Nd OpenSSH SSH client configuration files
46 .Nm /etc/ssh/ssh_config
49 obtains configuration data from the following sources in
52 .Bl -enum -offset indent -compact
56 user's configuration file
59 system-wide configuration file
60 .Pq Pa /etc/ssh/ssh_config
63 For each parameter, the first obtained value
65 The configuration files contain sections separated by
67 specifications, and that section is only applied for hosts that
68 match one of the patterns given in the specification.
69 The matched host name is the one given on the command line.
71 Since the first obtained value for each parameter is used, more
72 host-specific declarations should be given near the beginning of the
73 file, and general defaults at the end.
75 The configuration file has the following format:
77 Empty lines and lines starting with
80 Otherwise a line is of the format
81 .Dq keyword arguments .
82 Configuration options may be separated by whitespace or
83 optional whitespace and exactly one
85 the latter format is useful to avoid the need to quote whitespace
86 when specifying configuration options using the
93 Arguments may optionally be enclosed in double quotes
95 in order to represent arguments containing spaces.
98 keywords and their meanings are as follows (note that
99 keywords are case-insensitive and arguments are case-sensitive):
102 Restricts the following declarations (up to the next
104 keyword) to be only for those hosts that match one of the patterns
105 given after the keyword.
106 If more than one pattern is provided, they should be separated by whitespace.
109 as a pattern can be used to provide global
110 defaults for all hosts.
113 argument given on the command line (i.e. the name is not converted to
114 a canonicalized host name before matching).
116 A pattern entry may be negated by prefixing it with an exclamation mark
118 If a negated entry is matched, then the
120 entry is ignored, regardless of whether any other patterns on the line
122 Negated matches are therefore useful to provide exceptions for wildcard
127 for more information on patterns.
129 Specifies which address family to use when connecting.
139 passphrase/password querying will be disabled.
140 This option is useful in scripts and other batch jobs where no user
141 is present to supply the password.
149 Use the specified address on the local machine as the source address of
151 Only useful on systems with more than one address.
152 Note that this option does not work if
153 .Cm UsePrivilegedPort
156 .It Cm ChallengeResponseAuthentication
157 Specifies whether to use challenge-response authentication.
158 The argument to this keyword must be
165 If this flag is set to
168 will additionally check the host IP address in the
171 This allows ssh to detect if a host key changed due to DNS spoofing.
172 If the option is set to
174 the check will not be executed.
178 Specifies the cipher to use for encrypting the session
179 in protocol version 1.
187 is only supported in the
189 client for interoperability with legacy protocol 1 implementations
190 that do not support the
193 Its use is strongly discouraged due to cryptographic weaknesses.
197 Specifies the ciphers allowed for protocol version 2
198 in order of preference.
199 Multiple ciphers must be comma-separated.
200 The supported ciphers are
208 .Dq aes128-gcm@openssh.com ,
209 .Dq aes256-gcm@openssh.com ,
217 .Bd -literal -offset 3n
218 aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,
219 aes128-gcm@openssh.com,aes256-gcm@openssh.com,
220 aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,
223 .It Cm ClearAllForwardings
224 Specifies that all local, remote, and dynamic port forwardings
225 specified in the configuration files or on the command line be
227 This option is primarily useful when used from the
229 command line to clear port forwardings set in
230 configuration files, and is automatically set by
241 Specifies whether to use compression.
248 .It Cm CompressionLevel
249 Specifies the compression level to use if compression is enabled.
250 The argument must be an integer from 1 (fast) to 9 (slow, best).
251 The default level is 6, which is good for most applications.
252 The meaning of the values is the same as in
254 Note that this option applies to protocol version 1 only.
255 .It Cm ConnectionAttempts
256 Specifies the number of tries (one per second) to make before exiting.
257 The argument must be an integer.
258 This may be useful in scripts if the connection sometimes fails.
260 .It Cm ConnectTimeout
261 Specifies the timeout (in seconds) used when connecting to the
262 SSH server, instead of using the default system TCP timeout.
263 This value is used only when the target is down or really unreachable,
264 not when it refuses the connection.
266 Enables the sharing of multiple sessions over a single network connection.
270 will listen for connections on a control socket specified using the
273 Additional sessions can connect to this socket using the same
280 These sessions will try to reuse the master instance's network connection
281 rather than initiating new ones, but will fall back to connecting normally
282 if the control socket does not exist, or is not listening.
287 to listen for control connections, but require confirmation using the
289 program before they are accepted (see
295 ssh will continue without connecting to a master instance.
299 forwarding is supported over these multiplexed connections, however the
300 display and agent forwarded will be the one belonging to the master
301 connection i.e. it is not possible to forward multiple displays or agents.
303 Two additional options allow for opportunistic multiplexing: try to use a
304 master connection but fall back to creating a new one if one does not already
310 The latter requires confirmation like the
314 Specify the path to the control socket used for connection sharing as described
317 section above or the string
319 to disable connection sharing.
322 will be substituted by the first component of the local host name,
324 will be substituted by the local host name (including any domain name),
326 will be substituted by the target host name,
328 will be substituted by the original target host name
329 specified on the command line,
333 by the remote login username, and
335 by the username of the user running
337 It is recommended that any
339 used for opportunistic connection sharing include
340 at least %h, %p, and %r.
341 This ensures that shared connections are uniquely identified.
342 .It Cm ControlPersist
343 When used in conjunction with
345 specifies that the master connection should remain open
346 in the background (waiting for future client connections)
347 after the initial client connection has been closed.
350 then the master connection will not be placed into the background,
351 and will close as soon as the initial client connection is closed.
354 then the master connection will remain in the background indefinitely
355 (until killed or closed via a mechanism such as the
359 If set to a time in seconds, or a time in any of the formats documented in
361 then the backgrounded master connection will automatically terminate
362 after it has remained idle (with no client connections) for the
364 .It Cm DynamicForward
365 Specifies that a TCP port on the local machine be forwarded
366 over the secure channel, and the application
367 protocol is then used to determine where to connect to from the
372 .Oo Ar bind_address : Oc Ar port .
374 IPv6 addresses can be specified by enclosing addresses in square brackets.
375 By default, the local port is bound in accordance with the
380 may be used to bind the connection to a specific address.
385 indicates that the listening port be bound for local use only, while an
388 indicates that the port should be available from all interfaces.
390 Currently the SOCKS4 and SOCKS5 protocols are supported, and
392 will act as a SOCKS server.
393 Multiple forwardings may be specified, and
394 additional forwardings can be given on the command line.
395 Only the superuser can forward privileged ports.
396 .It Cm EnableSSHKeysign
397 Setting this option to
399 in the global client configuration file
400 .Pa /etc/ssh/ssh_config
401 enables the use of the helper program
404 .Cm HostbasedAuthentication .
411 This option should be placed in the non-hostspecific section.
414 for more information.
416 Sets the escape character (default:
418 The escape character can also
419 be set on the command line.
420 The argument should be a single character,
422 followed by a letter, or
424 to disable the escape
425 character entirely (making the connection transparent for binary
427 .It Cm ExitOnForwardFailure
430 should terminate the connection if it cannot set up all requested
431 dynamic, tunnel, local, and remote port forwardings.
439 Specifies whether the connection to the authentication agent (if any)
440 will be forwarded to the remote machine.
448 Agent forwarding should be enabled with caution.
449 Users with the ability to bypass file permissions on the remote host
450 (for the agent's Unix-domain socket)
451 can access the local agent through the forwarded connection.
452 An attacker cannot obtain key material from the agent,
453 however they can perform operations on the keys that enable them to
454 authenticate using the identities loaded into the agent.
456 Specifies whether X11 connections will be automatically redirected
457 over the secure channel and
467 X11 forwarding should be enabled with caution.
468 Users with the ability to bypass file permissions on the remote host
469 (for the user's X11 authorization database)
470 can access the local X11 display through the forwarded connection.
471 An attacker may then be able to perform activities such as keystroke monitoring
473 .Cm ForwardX11Trusted
474 option is also enabled.
475 .It Cm ForwardX11Timeout
476 Specify a timeout for untrusted X11 forwarding
477 using the format described in the
481 X11 connections received by
483 after this time will be refused.
484 The default is to disable untrusted X11 forwarding after twenty minutes has
486 .It Cm ForwardX11Trusted
487 If this option is set to
489 remote X11 clients will have full access to the original X11 display.
491 If this option is set to
493 remote X11 clients will be considered untrusted and prevented
494 from stealing or tampering with data belonging to trusted X11
498 token used for the session will be set to expire after 20 minutes.
499 Remote clients will be refused access after this time.
504 See the X11 SECURITY extension specification for full details on
505 the restrictions imposed on untrusted clients.
507 Specifies whether remote hosts are allowed to connect to local
511 binds local port forwardings to the loopback address.
512 This prevents other remote hosts from connecting to forwarded ports.
514 can be used to specify that ssh
515 should bind local port forwardings to the wildcard address,
516 thus allowing remote hosts to connect to forwarded ports.
523 .It Cm GlobalKnownHostsFile
524 Specifies one or more files to use for the global
525 host key database, separated by whitespace.
527 .Pa /etc/ssh/ssh_known_hosts ,
528 .Pa /etc/ssh/ssh_known_hosts2 .
529 .It Cm GSSAPIAuthentication
530 Specifies whether user authentication based on GSSAPI is allowed.
533 Note that this option applies to protocol version 2 only.
534 .It Cm GSSAPIDelegateCredentials
535 Forward (delegate) credentials to the server.
538 Note that this option applies to protocol version 2 only.
539 .It Cm HashKnownHosts
542 should hash host names and addresses when they are added to
543 .Pa ~/.ssh/known_hosts .
544 These hashed names may be used normally by
548 but they do not reveal identifying information should the file's contents
552 Note that existing names and addresses in known hosts files
553 will not be converted automatically,
554 but may be manually hashed using
556 .It Cm HostbasedAuthentication
557 Specifies whether to try rhosts based authentication with public key
565 This option applies to protocol version 2 only and
567 .Cm RhostsRSAAuthentication .
568 .It Cm HostKeyAlgorithms
569 Specifies the protocol version 2 host key algorithms
570 that the client wants to use in order of preference.
571 The default for this option is:
572 .Bd -literal -offset 3n
573 ecdsa-sha2-nistp256-cert-v01@openssh.com,
574 ecdsa-sha2-nistp384-cert-v01@openssh.com,
575 ecdsa-sha2-nistp521-cert-v01@openssh.com,
576 ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,
577 ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,
578 ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
582 If hostkeys are known for the destination host then this default is modified
583 to prefer their algorithms.
585 Specifies an alias that should be used instead of the
586 real host name when looking up or saving the host key
587 in the host key database files.
588 This option is useful for tunneling SSH connections
589 or for multiple servers running on a single host.
591 Specifies the real host name to log into.
592 This can be used to specify nicknames or abbreviations for hosts.
593 If the hostname contains the character sequence
595 then this will be replaced with the host name specified on the command line
596 (this is useful for manipulating unqualified names).
597 The default is the name given on the command line.
598 Numeric IP addresses are also permitted (both on the command line and in
601 .It Cm IdentitiesOnly
604 should only use the authentication identity files configured in the
611 offers more identities.
612 The argument to this keyword must be
616 This option is intended for situations where ssh-agent
617 offers many different identities.
621 Specifies a file from which the user's DSA, ECDSA or RSA authentication
625 for protocol version 1, and
630 for protocol version 2.
631 Additionally, any identities represented by the authentication agent
632 will be used for authentication.
634 will try to load certificate information from the filename obtained by
637 to the path of a specified
640 The file name may use the tilde
641 syntax to refer to a user's home directory or one of the following
644 (local user's home directory),
650 (remote host name) or
654 It is possible to have
655 multiple identity files specified in configuration files; all these
656 identities will be tried in sequence.
659 directives will add to the list of identities tried (this behaviour
660 differs from that of other configuration directives).
662 Specifies the IPv4 type-of-service or DSCP class for connections.
689 This option may take one or two arguments, separated by whitespace.
690 If one argument is specified, it is used as the packet class unconditionally.
691 If two values are specified, the first is automatically selected for
692 interactive sessions and the second for non-interactive sessions.
695 for interactive sessions and
697 for non-interactive sessions.
698 .It Cm KbdInteractiveAuthentication
699 Specifies whether to use keyboard-interactive authentication.
700 The argument to this keyword must be
706 .It Cm KbdInteractiveDevices
707 Specifies the list of methods to use in keyboard-interactive authentication.
708 Multiple method names must be comma-separated.
709 The default is to use the server specified list.
710 The methods available vary depending on what the server supports.
711 For an OpenSSH server,
712 it may be zero or more of:
718 Specifies the available KEX (Key Exchange) algorithms.
719 Multiple algorithms must be comma-separated.
721 .Bd -literal -offset indent
722 ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,
723 diffie-hellman-group-exchange-sha256,
724 diffie-hellman-group-exchange-sha1,
725 diffie-hellman-group14-sha1,
726 diffie-hellman-group1-sha1
729 Specifies a command to execute on the local machine after successfully
730 connecting to the server.
731 The command string extends to the end of the line, and is executed with
733 The following escape character substitutions will be performed:
735 (local user's home directory),
741 (host name as provided on the command line),
745 (remote user name) or
749 The command is run synchronously and does not have access to the
753 It should not be used for interactive commands.
755 This directive is ignored unless
756 .Cm PermitLocalCommand
759 Specifies that a TCP port on the local machine be forwarded over
760 the secure channel to the specified host and port from the remote machine.
761 The first argument must be
763 .Oo Ar bind_address : Oc Ar port
765 and the second argument must be
766 .Ar host : Ns Ar hostport .
767 IPv6 addresses can be specified by enclosing addresses in square brackets.
768 Multiple forwardings may be specified, and additional forwardings can be
769 given on the command line.
770 Only the superuser can forward privileged ports.
771 By default, the local port is bound in accordance with the
776 may be used to bind the connection to a specific address.
781 indicates that the listening port be bound for local use only, while an
784 indicates that the port should be available from all interfaces.
786 Gives the verbosity level that is used when logging messages from
788 The possible values are:
789 QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2, and DEBUG3.
791 DEBUG and DEBUG1 are equivalent.
792 DEBUG2 and DEBUG3 each specify higher levels of verbose output.
794 Specifies the MAC (message authentication code) algorithms
795 in order of preference.
796 The MAC algorithm is used in protocol version 2
797 for data integrity protection.
798 Multiple algorithms must be comma-separated.
799 The algorithms that contain
801 calculate the MAC after encryption (encrypt-then-mac).
802 These are considered safer and their use recommended.
804 .Bd -literal -offset indent
805 hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,
806 umac-64-etm@openssh.com,umac-128-etm@openssh.com,
807 hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,
808 hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,
809 hmac-md5-96-etm@openssh.com,
810 hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,
811 hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,
812 hmac-sha1-96,hmac-md5-96
814 .It Cm NoHostAuthenticationForLocalhost
815 This option can be used if the home directory is shared across machines.
816 In this case localhost will refer to a different machine on each of
817 the machines and the user will get many warnings about changed host keys.
818 However, this option disables host authentication for localhost.
819 The argument to this keyword must be
823 The default is to check the host key for localhost.
824 .It Cm NumberOfPasswordPrompts
825 Specifies the number of password prompts before giving up.
826 The argument to this keyword must be an integer.
828 .It Cm PasswordAuthentication
829 Specifies whether to use password authentication.
830 The argument to this keyword must be
836 .It Cm PermitLocalCommand
837 Allow local command execution via the
840 .Ic !\& Ns Ar command
849 .It Cm PKCS11Provider
850 Specifies which PKCS#11 provider to use.
851 The argument to this keyword is the PKCS#11 shared library
853 should use to communicate with a PKCS#11 token providing the user's
856 Specifies the port number to connect on the remote host.
858 .It Cm PreferredAuthentications
859 Specifies the order in which the client should try protocol 2
860 authentication methods.
861 This allows a client to prefer one method (e.g.\&
862 .Cm keyboard-interactive )
863 over another method (e.g.\&
866 .Bd -literal -offset indent
867 gssapi-with-mic,hostbased,publickey,
868 keyboard-interactive,password
871 Specifies the protocol versions
873 should support in order of preference.
874 The possible values are
878 Multiple versions must be comma-separated.
879 When this option is set to
882 will try version 2 and fall back to version 1
883 if version 2 is not available.
887 Specifies the command to use to connect to the server.
889 string extends to the end of the line, and is executed with
891 In the command string, any occurrence of
893 will be substituted by the host name to
898 by the remote user name.
899 The command can be basically anything,
900 and should read from its standard input and write to its standard output.
901 It should eventually connect an
903 server running on some machine, or execute
906 Host key management will be done using the
907 HostName of the host being connected (defaulting to the name typed by
909 Setting the command to
911 disables this option entirely.
914 is not available for connects with a proxy command.
916 This directive is useful in conjunction with
918 and its proxy support.
919 For example, the following directive would connect via an HTTP proxy at
921 .Bd -literal -offset 3n
922 ProxyCommand /usr/bin/nc -X connect -x 192.0.2.0:8080 %h %p
924 .It Cm PubkeyAuthentication
925 Specifies whether to try public key authentication.
926 The argument to this keyword must be
932 This option applies to protocol version 2 only.
934 Specifies the maximum amount of data that may be transmitted before the
935 session key is renegotiated.
936 The argument is the number of bytes, with an optional suffix of
941 to indicate Kilobytes, Megabytes, or Gigabytes, respectively.
942 The default is between
946 depending on the cipher.
947 This option applies to protocol version 2 only.
949 Specifies that a TCP port on the remote machine be forwarded over
950 the secure channel to the specified host and port from the local machine.
951 The first argument must be
953 .Oo Ar bind_address : Oc Ar port
955 and the second argument must be
956 .Ar host : Ns Ar hostport .
957 IPv6 addresses can be specified by enclosing addresses in square brackets.
958 Multiple forwardings may be specified, and additional
959 forwardings can be given on the command line.
960 Privileged ports can be forwarded only when
961 logging in as root on the remote machine.
967 the listen port will be dynamically allocated on the server and reported
968 to the client at run time.
972 is not specified, the default is to only bind to loopback addresses.
977 or an empty string, then the forwarding is requested to listen on all
981 will only succeed if the server's
983 option is enabled (see
984 .Xr sshd_config 5 ) .
986 Specifies whether to request a pseudo-tty for the session.
987 The argument may be one of:
989 (never request a TTY),
991 (always request a TTY when standard input is a TTY),
993 (always request a TTY) or
995 (request a TTY when opening a login session).
996 This option mirrors the
1002 .It Cm RhostsRSAAuthentication
1003 Specifies whether to try rhosts based authentication with RSA host
1005 The argument must be
1011 This option applies to protocol version 1 only and requires
1014 .It Cm RSAAuthentication
1015 Specifies whether to try RSA authentication.
1016 The argument to this keyword must be
1020 RSA authentication will only be
1021 attempted if the identity file exists, or an authentication agent is
1025 Note that this option applies to protocol version 1 only.
1027 Specifies what variables from the local
1029 should be sent to the server.
1030 Note that environment passing is only supported for protocol 2.
1031 The server must also support it, and the server must be configured to
1032 accept these environment variables.
1037 for how to configure the server.
1038 Variables are specified by name, which may contain wildcard characters.
1039 Multiple environment variables may be separated by whitespace or spread
1043 The default is not to send any environment variables.
1047 for more information on patterns.
1048 .It Cm ServerAliveCountMax
1049 Sets the number of server alive messages (see below) which may be
1052 receiving any messages back from the server.
1053 If this threshold is reached while server alive messages are being sent,
1054 ssh will disconnect from the server, terminating the session.
1055 It is important to note that the use of server alive messages is very
1059 The server alive messages are sent through the encrypted channel
1060 and therefore will not be spoofable.
1061 The TCP keepalive option enabled by
1064 The server alive mechanism is valuable when the client or
1065 server depend on knowing when a connection has become inactive.
1067 The default value is 3.
1069 .Cm ServerAliveInterval
1070 (see below) is set to 15 and
1071 .Cm ServerAliveCountMax
1072 is left at the default, if the server becomes unresponsive,
1073 ssh will disconnect after approximately 45 seconds.
1074 This option applies to protocol version 2 only.
1075 .It Cm ServerAliveInterval
1076 Sets a timeout interval in seconds after which if no data has been received
1079 will send a message through the encrypted
1080 channel to request a response from the server.
1082 is 0, indicating that these messages will not be sent to the server.
1083 This option applies to protocol version 2 only.
1084 .It Cm StrictHostKeyChecking
1085 If this flag is set to
1088 will never automatically add host keys to the
1089 .Pa ~/.ssh/known_hosts
1090 file, and refuses to connect to hosts whose host key has changed.
1091 This provides maximum protection against trojan horse attacks,
1092 though it can be annoying when the
1093 .Pa /etc/ssh/ssh_known_hosts
1094 file is poorly maintained or when connections to new hosts are
1096 This option forces the user to manually
1098 If this flag is set to
1100 ssh will automatically add new host keys to the
1101 user known hosts files.
1102 If this flag is set to
1105 will be added to the user known host files only after the user
1106 has confirmed that is what they really want to do, and
1107 ssh will refuse to connect to hosts whose host key has changed.
1109 known hosts will be verified automatically in all cases.
1110 The argument must be
1118 Specifies whether the system should send TCP keepalive messages to the
1120 If they are sent, death of the connection or crash of one
1121 of the machines will be properly noticed.
1122 However, this means that
1123 connections will die if the route is down temporarily, and some people
1128 (to send TCP keepalive messages), and the client will notice
1129 if the network goes down or the remote host dies.
1130 This is important in scripts, and many users want it too.
1132 To disable TCP keepalive messages, the value should be set to
1137 device forwarding between the client and the server.
1138 The argument must be
1148 requests the default tunnel mode, which is
1149 .Dq point-to-point .
1155 devices to open on the client
1160 The argument must be
1162 .Ar local_tun Op : Ar remote_tun .
1164 The devices may be specified by numerical ID or the keyword
1166 which uses the next available tunnel device.
1169 is not specified, it defaults to
1173 .It Cm UsePrivilegedPort
1174 Specifies whether to use a privileged port for outgoing connections.
1175 The argument must be
1184 must be setuid root.
1185 Note that this option must be set to
1188 .Cm RhostsRSAAuthentication
1191 Specifies the user to log in as.
1192 This can be useful when a different user name is used on different machines.
1193 This saves the trouble of
1194 having to remember to give the user name on the command line.
1195 .It Cm UserKnownHostsFile
1196 Specifies one or more files to use for the user
1197 host key database, separated by whitespace.
1199 .Pa ~/.ssh/known_hosts ,
1200 .Pa ~/.ssh/known_hosts2 .
1201 .It Cm VerifyHostKeyDNS
1202 Specifies whether to verify the remote key using DNS and SSHFP resource
1204 If this option is set to
1206 the client will implicitly trust keys that match a secure fingerprint
1208 Insecure fingerprints will be handled as if this option was set to
1210 If this option is set to
1212 information on fingerprint match will be displayed, but the user will still
1213 need to confirm new host keys according to the
1214 .Cm StrictHostKeyChecking
1216 The argument must be
1223 Note that this option applies to protocol version 2 only.
1226 .Sx VERIFYING HOST KEYS
1229 .It Cm VersionAddendum
1230 Specifies a string to append to the regular version string to identify
1231 OS- or site-specific modifications.
1233 .Dq FreeBSD-20130515 .
1234 .It Cm VisualHostKey
1235 If this flag is set to
1237 an ASCII art representation of the remote host key fingerprint is
1238 printed in addition to the hex fingerprint string at login and
1239 for unknown host keys.
1240 If this flag is set to
1242 no fingerprint strings are printed at login and
1243 only the hex fingerprint string will be printed for unknown host keys.
1246 .It Cm XAuthLocation
1247 Specifies the full pathname of the
1251 .Pa /usr/local/bin/xauth .
1256 consists of zero or more non-whitespace characters,
1258 (a wildcard that matches zero or more characters),
1261 (a wildcard that matches exactly one character).
1262 For example, to specify a set of declarations for any host in the
1265 the following pattern could be used:
1269 The following pattern
1270 would match any host in the 192.168.0.[0-9] network range:
1272 .Dl Host 192.168.0.?
1276 is a comma-separated list of patterns.
1277 Patterns within pattern-lists may be negated
1278 by preceding them with an exclamation mark
1281 to allow a key to be used from anywhere within an organisation
1285 the following entry (in authorized_keys) could be used:
1287 .Dl from=\&"!*.dialup.example.com,*.example.com\&"
1290 .It Pa ~/.ssh/config
1291 This is the per-user configuration file.
1292 The format of this file is described above.
1293 This file is used by the SSH client.
1294 Because of the potential for abuse, this file must have strict permissions:
1295 read/write for the user, and not accessible by others.
1296 .It Pa /etc/ssh/ssh_config
1297 Systemwide configuration file.
1298 This file provides defaults for those
1299 values that are not specified in the user's configuration file, and
1300 for those users who do not have a configuration file.
1301 This file must be world-readable.
1306 OpenSSH is a derivative of the original and free
1307 ssh 1.2.12 release by Tatu Ylonen.
1308 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
1309 Theo de Raadt and Dug Song
1310 removed many bugs, re-added newer features and
1312 Markus Friedl contributed the support for SSH
1313 protocol versions 1.5 and 2.0.