]> andersk Git - gssapi-openssh.git/blame_incremental - openssh/ssh_config.5
merged OpenSSH 4.7p1 to trunk
[gssapi-openssh.git] / openssh / ssh_config.5
... / ...
CommitLineData
1.\" -*- nroff -*-
2.\"
3.\" Author: Tatu Ylonen <ylo@cs.hut.fi>
4.\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
5.\" All rights reserved
6.\"
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".
12.\"
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.
16.\"
17.\" Redistribution and use in source and binary forms, with or without
18.\" modification, are permitted provided that the following conditions
19.\" are met:
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.
25.\"
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.
36.\"
37.\" $OpenBSD: ssh_config.5,v 1.102 2007/08/15 12:13:41 stevesk Exp $
38.Dd $Mdocdate: August 15 2007 $
39.Dt SSH_CONFIG 5
40.Os
41.Sh NAME
42.Nm ssh_config
43.Nd OpenSSH SSH client configuration files
44.Sh SYNOPSIS
45.Nm ~/.ssh/config
46.Nm /etc/ssh/ssh_config
47.Sh DESCRIPTION
48.Xr ssh 1
49obtains configuration data from the following sources in
50the following order:
51.Pp
52.Bl -enum -offset indent -compact
53.It
54command-line options
55.It
56user's configuration file
57.Pq Pa ~/.ssh/config
58.It
59GSSAPI configuration file
60.Pq Pa $HOME/.ssh/config.gssapi
61.It
62Kerberos configuration file
63.Pq Pa $HOME/.ssh/config.krb
64.It
65system-wide configuration file
66.Pq Pa /etc/ssh/ssh_config
67.El
68.Pp
69For each parameter, the first obtained value
70will be used.
71The configuration files contain sections separated by
72.Dq Host
73specifications, and that section is only applied for hosts that
74match one of the patterns given in the specification.
75The matched host name is the one given on the command line.
76.Pp
77Since the first obtained value for each parameter is used, more
78host-specific declarations should be given near the beginning of the
79file, and general defaults at the end.
80.Pp
81The configuration file has the following format:
82.Pp
83Empty lines and lines starting with
84.Ql #
85are comments.
86Otherwise a line is of the format
87.Dq keyword arguments .
88Configuration options may be separated by whitespace or
89optional whitespace and exactly one
90.Ql = ;
91the latter format is useful to avoid the need to quote whitespace
92when specifying configuration options using the
93.Nm ssh ,
94.Nm scp ,
95and
96.Nm sftp
97.Fl o
98option.
99Arguments may optionally be enclosed in double quotes
100.Pq \&"
101in order to represent arguments containing spaces.
102.Pp
103The possible
104keywords and their meanings are as follows (note that
105keywords are case-insensitive and arguments are case-sensitive):
106.Bl -tag -width Ds
107.It Cm Host
108Restricts the following declarations (up to the next
109.Cm Host
110keyword) to be only for those hosts that match one of the patterns
111given after the keyword.
112A single
113.Ql *
114as a pattern can be used to provide global
115defaults for all hosts.
116The host is the
117.Ar hostname
118argument given on the command line (i.e. the name is not converted to
119a canonicalized host name before matching).
120.Pp
121See
122.Sx PATTERNS
123for more information on patterns.
124.It Cm AddressFamily
125Specifies which address family to use when connecting.
126Valid arguments are
127.Dq any ,
128.Dq inet
129(use IPv4 only), or
130.Dq inet6
131(use IPv6 only).
132.It Cm BatchMode
133If set to
134.Dq yes ,
135passphrase/password querying will be disabled.
136This option is useful in scripts and other batch jobs where no user
137is present to supply the password.
138The argument must be
139.Dq yes
140or
141.Dq no .
142The default is
143.Dq no .
144.It Cm BindAddress
145Use the specified address on the local machine as the source address of
146the connection.
147Only useful on systems with more than one address.
148Note that this option does not work if
149.Cm UsePrivilegedPort
150is set to
151.Dq yes .
152.It Cm ChallengeResponseAuthentication
153Specifies whether to use challenge-response authentication.
154The argument to this keyword must be
155.Dq yes
156or
157.Dq no .
158The default is
159.Dq yes .
160.It Cm CheckHostIP
161If this flag is set to
162.Dq yes ,
163.Xr ssh 1
164will additionally check the host IP address in the
165.Pa known_hosts
166file.
167This allows ssh to detect if a host key changed due to DNS spoofing.
168If the option is set to
169.Dq no ,
170the check will not be executed.
171The default is
172.Dq yes .
173.It Cm Cipher
174Specifies the cipher to use for encrypting the session
175in protocol version 1.
176Currently,
177.Dq blowfish ,
178.Dq 3des ,
179and
180.Dq des
181are supported.
182.Ar des
183is only supported in the
184.Xr ssh 1
185client for interoperability with legacy protocol 1 implementations
186that do not support the
187.Ar 3des
188cipher.
189Its use is strongly discouraged due to cryptographic weaknesses.
190The default is
191.Dq 3des .
192.It Cm Ciphers
193Specifies the ciphers allowed for protocol version 2
194in order of preference.
195Multiple ciphers must be comma-separated.
196The supported ciphers are
197.Dq 3des-cbc ,
198.Dq aes128-cbc ,
199.Dq aes192-cbc ,
200.Dq aes256-cbc ,
201.Dq aes128-ctr ,
202.Dq aes192-ctr ,
203.Dq aes256-ctr ,
204.Dq arcfour128 ,
205.Dq arcfour256 ,
206.Dq arcfour ,
207.Dq blowfish-cbc ,
208and
209.Dq cast128-cbc .
210The default is:
211.Bd -literal -offset 3n
212aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,
213arcfour256,arcfour,aes192-cbc,aes256-cbc,aes128-ctr,
214aes192-ctr,aes256-ctr
215.Ed
216.It Cm ClearAllForwardings
217Specifies that all local, remote, and dynamic port forwardings
218specified in the configuration files or on the command line be
219cleared.
220This option is primarily useful when used from the
221.Xr ssh 1
222command line to clear port forwardings set in
223configuration files, and is automatically set by
224.Xr scp 1
225and
226.Xr sftp 1 .
227The argument must be
228.Dq yes
229or
230.Dq no .
231The default is
232.Dq no .
233.It Cm Compression
234Specifies whether to use compression.
235The argument must be
236.Dq yes
237or
238.Dq no .
239The default is
240.Dq no .
241.It Cm CompressionLevel
242Specifies the compression level to use if compression is enabled.
243The argument must be an integer from 1 (fast) to 9 (slow, best).
244The default level is 6, which is good for most applications.
245The meaning of the values is the same as in
246.Xr gzip 1 .
247Note that this option applies to protocol version 1 only.
248.It Cm ConnectionAttempts
249Specifies the number of tries (one per second) to make before exiting.
250The argument must be an integer.
251This may be useful in scripts if the connection sometimes fails.
252The default is 1.
253.It Cm ConnectTimeout
254Specifies the timeout (in seconds) used when connecting to the
255SSH server, instead of using the default system TCP timeout.
256This value is used only when the target is down or really unreachable,
257not when it refuses the connection.
258.It Cm ControlMaster
259Enables the sharing of multiple sessions over a single network connection.
260When set to
261.Dq yes ,
262.Xr ssh 1
263will listen for connections on a control socket specified using the
264.Cm ControlPath
265argument.
266Additional sessions can connect to this socket using the same
267.Cm ControlPath
268with
269.Cm ControlMaster
270set to
271.Dq no
272(the default).
273These sessions will try to reuse the master instance's network connection
274rather than initiating new ones, but will fall back to connecting normally
275if the control socket does not exist, or is not listening.
276.Pp
277Setting this to
278.Dq ask
279will cause ssh
280to listen for control connections, but require confirmation using the
281.Ev SSH_ASKPASS
282program before they are accepted (see
283.Xr ssh-add 1
284for details).
285If the
286.Cm ControlPath
287cannot be opened,
288ssh will continue without connecting to a master instance.
289.Pp
290X11 and
291.Xr ssh-agent 1
292forwarding is supported over these multiplexed connections, however the
293display and agent forwarded will be the one belonging to the master
294connection i.e. it is not possible to forward multiple displays or agents.
295.Pp
296Two additional options allow for opportunistic multiplexing: try to use a
297master connection but fall back to creating a new one if one does not already
298exist.
299These options are:
300.Dq auto
301and
302.Dq autoask .
303The latter requires confirmation like the
304.Dq ask
305option.
306.It Cm ControlPath
307Specify the path to the control socket used for connection sharing as described
308in the
309.Cm ControlMaster
310section above or the string
311.Dq none
312to disable connection sharing.
313In the path,
314.Ql %l
315will be substituted by the local host name,
316.Ql %h
317will be substituted by the target host name,
318.Ql %p
319the port, and
320.Ql %r
321by the remote login username.
322It is recommended that any
323.Cm ControlPath
324used for opportunistic connection sharing include
325at least %h, %p, and %r.
326This ensures that shared connections are uniquely identified.
327.It Cm DynamicForward
328Specifies that a TCP port on the local machine be forwarded
329over the secure channel, and the application
330protocol is then used to determine where to connect to from the
331remote machine.
332.Pp
333The argument must be
334.Sm off
335.Oo Ar bind_address : Oc Ar port .
336.Sm on
337IPv6 addresses can be specified by enclosing addresses in square brackets or
338by using an alternative syntax:
339.Oo Ar bind_address Ns / Oc Ns Ar port .
340By default, the local port is bound in accordance with the
341.Cm GatewayPorts
342setting.
343However, an explicit
344.Ar bind_address
345may be used to bind the connection to a specific address.
346The
347.Ar bind_address
348of
349.Dq localhost
350indicates that the listening port be bound for local use only, while an
351empty address or
352.Sq *
353indicates that the port should be available from all interfaces.
354.Pp
355Currently the SOCKS4 and SOCKS5 protocols are supported, and
356.Xr ssh 1
357will act as a SOCKS server.
358Multiple forwardings may be specified, and
359additional forwardings can be given on the command line.
360Only the superuser can forward privileged ports.
361.It Cm EnableSSHKeysign
362Setting this option to
363.Dq yes
364in the global client configuration file
365.Pa /etc/ssh/ssh_config
366enables the use of the helper program
367.Xr ssh-keysign 8
368during
369.Cm HostbasedAuthentication .
370The argument must be
371.Dq yes
372or
373.Dq no .
374The default is
375.Dq no .
376This option should be placed in the non-hostspecific section.
377See
378.Xr ssh-keysign 8
379for more information.
380.It Cm EscapeChar
381Sets the escape character (default:
382.Ql ~ ) .
383The escape character can also
384be set on the command line.
385The argument should be a single character,
386.Ql ^
387followed by a letter, or
388.Dq none
389to disable the escape
390character entirely (making the connection transparent for binary
391data).
392.It Cm ExitOnForwardFailure
393Specifies whether
394.Xr ssh 1
395should terminate the connection if it cannot set up all requested
396dynamic, tunnel, local, and remote port forwardings.
397The argument must be
398.Dq yes
399or
400.Dq no .
401The default is
402.Dq no .
403.It Cm ForwardAgent
404Specifies whether the connection to the authentication agent (if any)
405will be forwarded to the remote machine.
406The argument must be
407.Dq yes
408or
409.Dq no .
410The default is
411.Dq no .
412.Pp
413Agent forwarding should be enabled with caution.
414Users with the ability to bypass file permissions on the remote host
415(for the agent's Unix-domain socket)
416can access the local agent through the forwarded connection.
417An attacker cannot obtain key material from the agent,
418however they can perform operations on the keys that enable them to
419authenticate using the identities loaded into the agent.
420.It Cm ForwardX11
421Specifies whether X11 connections will be automatically redirected
422over the secure channel and
423.Ev DISPLAY
424set.
425The argument must be
426.Dq yes
427or
428.Dq no .
429The default is
430.Dq no .
431.Pp
432X11 forwarding should be enabled with caution.
433Users with the ability to bypass file permissions on the remote host
434(for the user's X11 authorization database)
435can access the local X11 display through the forwarded connection.
436An attacker may then be able to perform activities such as keystroke monitoring
437if the
438.Cm ForwardX11Trusted
439option is also enabled.
440.It Cm ForwardX11Trusted
441If this option is set to
442.Dq yes ,
443remote X11 clients will have full access to the original X11 display.
444.Pp
445If this option is set to
446.Dq no ,
447remote X11 clients will be considered untrusted and prevented
448from stealing or tampering with data belonging to trusted X11
449clients.
450Furthermore, the
451.Xr xauth 1
452token used for the session will be set to expire after 20 minutes.
453Remote clients will be refused access after this time.
454.Pp
455The default is
456.Dq no .
457.Pp
458See the X11 SECURITY extension specification for full details on
459the restrictions imposed on untrusted clients.
460.It Cm GatewayPorts
461Specifies whether remote hosts are allowed to connect to local
462forwarded ports.
463By default,
464.Xr ssh 1
465binds local port forwardings to the loopback address.
466This prevents other remote hosts from connecting to forwarded ports.
467.Cm GatewayPorts
468can be used to specify that ssh
469should bind local port forwardings to the wildcard address,
470thus allowing remote hosts to connect to forwarded ports.
471The argument must be
472.Dq yes
473or
474.Dq no .
475The default is
476.Dq no .
477.It Cm GlobalKnownHostsFile
478Specifies a file to use for the global
479host key database instead of
480.Pa /etc/ssh/ssh_known_hosts .
481.It Cm GSSAPIAuthentication
482Specifies whether user authentication based on GSSAPI is allowed.
483The default is
484.Dq yes .
485Note that this option applies to protocol version 2 only.
486.It Cm GSSAPIKeyExchange
487Specifies whether key exchange based on GSSAPI may be used. When using
488GSSAPI key exchange the server need not have a host key.
489The default is
490.Dq yes .
491Note that this option applies to protocol version 2 only.
492.It Cm GSSAPIDelegateCredentials
493Forward (delegate) credentials to the server.
494The default is
495.Dq yes .
496Note that this option applies to protocol version 2 only.
497.It Cm GSSAPITrustDns
498Set to
499.Dq yes
500to indicate that the DNS is trusted to securely canonicalize
501the name of the host being connected to. If
502.Dq no ,
503the hostname entered on the
504command line will be passed untouched to the GSSAPI library.
505The default is
506.Dq yes .
507This option only applies to protocol version 2 connections using GSSAPI.
508.It Cm HashKnownHosts
509Indicates that
510.Xr ssh 1
511should hash host names and addresses when they are added to
512.Pa ~/.ssh/known_hosts .
513These hashed names may be used normally by
514.Xr ssh 1
515and
516.Xr sshd 8 ,
517but they do not reveal identifying information should the file's contents
518be disclosed.
519The default is
520.Dq no .
521Note that existing names and addresses in known hosts files
522will not be converted automatically,
523but may be manually hashed using
524.Xr ssh-keygen 1 .
525.It Cm HostbasedAuthentication
526Specifies whether to try rhosts based authentication with public key
527authentication.
528The argument must be
529.Dq yes
530or
531.Dq no .
532The default is
533.Dq no .
534This option applies to protocol version 2 only and
535is similar to
536.Cm RhostsRSAAuthentication .
537.It Cm HostKeyAlgorithms
538Specifies the protocol version 2 host key algorithms
539that the client wants to use in order of preference.
540The default for this option is:
541.Dq ssh-rsa,ssh-dss .
542.It Cm HostKeyAlias
543Specifies an alias that should be used instead of the
544real host name when looking up or saving the host key
545in the host key database files.
546This option is useful for tunneling SSH connections
547or for multiple servers running on a single host.
548.It Cm HostName
549Specifies the real host name to log into.
550This can be used to specify nicknames or abbreviations for hosts.
551The default is the name given on the command line.
552Numeric IP addresses are also permitted (both on the command line and in
553.Cm HostName
554specifications).
555.It Cm IdentitiesOnly
556Specifies that
557.Xr ssh 1
558should only use the authentication identity files configured in the
559.Nm
560files,
561even if
562.Xr ssh-agent 1
563offers more identities.
564The argument to this keyword must be
565.Dq yes
566or
567.Dq no .
568This option is intended for situations where ssh-agent
569offers many different identities.
570The default is
571.Dq no .
572.It Cm IdentityFile
573Specifies a file from which the user's RSA or DSA authentication identity
574is read.
575The default is
576.Pa ~/.ssh/identity
577for protocol version 1, and
578.Pa ~/.ssh/id_rsa
579and
580.Pa ~/.ssh/id_dsa
581for protocol version 2.
582Additionally, any identities represented by the authentication agent
583will be used for authentication.
584.Pp
585The file name may use the tilde
586syntax to refer to a user's home directory or one of the following
587escape characters:
588.Ql %d
589(local user's home directory),
590.Ql %u
591(local user name),
592.Ql %l
593(local host name),
594.Ql %h
595(remote host name) or
596.Ql %r
597(remote user name).
598.Pp
599It is possible to have
600multiple identity files specified in configuration files; all these
601identities will be tried in sequence.
602.It Cm KbdInteractiveDevices
603Specifies the list of methods to use in keyboard-interactive authentication.
604Multiple method names must be comma-separated.
605The default is to use the server specified list.
606The methods available vary depending on what the server supports.
607For an OpenSSH server,
608it may be zero or more of:
609.Dq bsdauth ,
610.Dq pam ,
611and
612.Dq skey .
613.It Cm LocalCommand
614Specifies a command to execute on the local machine after successfully
615connecting to the server.
616The command string extends to the end of the line, and is executed with
617.Pa /bin/sh .
618This directive is ignored unless
619.Cm PermitLocalCommand
620has been enabled.
621.It Cm LocalForward
622Specifies that a TCP port on the local machine be forwarded over
623the secure channel to the specified host and port from the remote machine.
624The first argument must be
625.Sm off
626.Oo Ar bind_address : Oc Ar port
627.Sm on
628and the second argument must be
629.Ar host : Ns Ar hostport .
630IPv6 addresses can be specified by enclosing addresses in square brackets or
631by using an alternative syntax:
632.Oo Ar bind_address Ns / Oc Ns Ar port
633and
634.Ar host Ns / Ns Ar hostport .
635Multiple forwardings may be specified, and additional forwardings can be
636given on the command line.
637Only the superuser can forward privileged ports.
638By default, the local port is bound in accordance with the
639.Cm GatewayPorts
640setting.
641However, an explicit
642.Ar bind_address
643may be used to bind the connection to a specific address.
644The
645.Ar bind_address
646of
647.Dq localhost
648indicates that the listening port be bound for local use only, while an
649empty address or
650.Sq *
651indicates that the port should be available from all interfaces.
652.It Cm LogLevel
653Gives the verbosity level that is used when logging messages from
654.Xr ssh 1 .
655The possible values are:
656QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2, and DEBUG3.
657The default is INFO.
658DEBUG and DEBUG1 are equivalent.
659DEBUG2 and DEBUG3 each specify higher levels of verbose output.
660.It Cm MACs
661Specifies the MAC (message authentication code) algorithms
662in order of preference.
663The MAC algorithm is used in protocol version 2
664for data integrity protection.
665Multiple algorithms must be comma-separated.
666The default is:
667.Bd -literal -offset indent
668hmac-md5,hmac-sha1,umac-64@openssh.com,
669hmac-ripemd160,hmac-sha1-96,hmac-md5-96
670.Ed
671.It Cm NoHostAuthenticationForLocalhost
672This option can be used if the home directory is shared across machines.
673In this case localhost will refer to a different machine on each of
674the machines and the user will get many warnings about changed host keys.
675However, this option disables host authentication for localhost.
676The argument to this keyword must be
677.Dq yes
678or
679.Dq no .
680The default is to check the host key for localhost.
681.It Cm NumberOfPasswordPrompts
682Specifies the number of password prompts before giving up.
683The argument to this keyword must be an integer.
684The default is 3.
685.It Cm PasswordAuthentication
686Specifies whether to use password authentication.
687The argument to this keyword must be
688.Dq yes
689or
690.Dq no .
691The default is
692.Dq yes .
693.It Cm PermitLocalCommand
694Allow local command execution via the
695.Ic LocalCommand
696option or using the
697.Ic !\& Ns Ar command
698escape sequence in
699.Xr ssh 1 .
700The argument must be
701.Dq yes
702or
703.Dq no .
704The default is
705.Dq no .
706.It Cm Port
707Specifies the port number to connect on the remote host.
708The default is 22.
709.It Cm PreferredAuthentications
710Specifies the order in which the client should try protocol 2
711authentication methods.
712This allows a client to prefer one method (e.g.\&
713.Cm keyboard-interactive )
714over another method (e.g.\&
715.Cm password )
716The default for this option is:
717.Do gssapi-keyex ,
718external-keyx,
719gssapi-with-mic,
720hostbased,
721publickey,
722keyboard-interactive,
723password
724.Dc .
725.It Cm Protocol
726Specifies the protocol versions
727.Xr ssh 1
728should support in order of preference.
729The possible values are
730.Sq 1
731and
732.Sq 2 .
733Multiple versions must be comma-separated.
734The default is
735.Dq 2,1 .
736This means that ssh
737tries version 2 and falls back to version 1
738if version 2 is not available.
739.It Cm ProxyCommand
740Specifies the command to use to connect to the server.
741The command
742string extends to the end of the line, and is executed with
743.Pa /bin/sh .
744In the command string,
745.Ql %h
746will be substituted by the host name to
747connect and
748.Ql %p
749by the port.
750The command can be basically anything,
751and should read from its standard input and write to its standard output.
752It should eventually connect an
753.Xr sshd 8
754server running on some machine, or execute
755.Ic sshd -i
756somewhere.
757Host key management will be done using the
758HostName of the host being connected (defaulting to the name typed by
759the user).
760Setting the command to
761.Dq none
762disables this option entirely.
763Note that
764.Cm CheckHostIP
765is not available for connects with a proxy command.
766.Pp
767This directive is useful in conjunction with
768.Xr nc 1
769and its proxy support.
770For example, the following directive would connect via an HTTP proxy at
771192.0.2.0:
772.Bd -literal -offset 3n
773ProxyCommand /usr/bin/nc -X connect -x 192.0.2.0:8080 %h %p
774.Ed
775.It Cm PubkeyAuthentication
776Specifies whether to try public key authentication.
777The argument to this keyword must be
778.Dq yes
779or
780.Dq no .
781The default is
782.Dq yes .
783This option applies to protocol version 2 only.
784.It Cm RekeyLimit
785Specifies the maximum amount of data that may be transmitted before the
786session key is renegotiated.
787The argument is the number of bytes, with an optional suffix of
788.Sq K ,
789.Sq M ,
790or
791.Sq G
792to indicate Kilobytes, Megabytes, or Gigabytes, respectively.
793The default is between
794.Sq 1G
795and
796.Sq 4G ,
797depending on the cipher.
798This option applies to protocol version 2 only.
799.It Cm RemoteForward
800Specifies that a TCP port on the remote machine be forwarded over
801the secure channel to the specified host and port from the local machine.
802The first argument must be
803.Sm off
804.Oo Ar bind_address : Oc Ar port
805.Sm on
806and the second argument must be
807.Ar host : Ns Ar hostport .
808IPv6 addresses can be specified by enclosing addresses in square brackets
809or by using an alternative syntax:
810.Oo Ar bind_address Ns / Oc Ns Ar port
811and
812.Ar host Ns / Ns Ar hostport .
813Multiple forwardings may be specified, and additional
814forwardings can be given on the command line.
815Only the superuser can forward privileged ports.
816.Pp
817If the
818.Ar bind_address
819is not specified, the default is to only bind to loopback addresses.
820If the
821.Ar bind_address
822is
823.Ql *
824or an empty string, then the forwarding is requested to listen on all
825interfaces.
826Specifying a remote
827.Ar bind_address
828will only succeed if the server's
829.Cm GatewayPorts
830option is enabled (see
831.Xr sshd_config 5 ) .
832.It Cm RhostsRSAAuthentication
833Specifies whether to try rhosts based authentication with RSA host
834authentication.
835The argument must be
836.Dq yes
837or
838.Dq no .
839The default is
840.Dq no .
841This option applies to protocol version 1 only and requires
842.Xr ssh 1
843to be setuid root.
844.It Cm RSAAuthentication
845Specifies whether to try RSA authentication.
846The argument to this keyword must be
847.Dq yes
848or
849.Dq no .
850RSA authentication will only be
851attempted if the identity file exists, or an authentication agent is
852running.
853The default is
854.Dq yes .
855Note that this option applies to protocol version 1 only.
856.It Cm SendEnv
857Specifies what variables from the local
858.Xr environ 7
859should be sent to the server.
860Note that environment passing is only supported for protocol 2.
861The server must also support it, and the server must be configured to
862accept these environment variables.
863Refer to
864.Cm AcceptEnv
865in
866.Xr sshd_config 5
867for how to configure the server.
868Variables are specified by name, which may contain wildcard characters.
869Multiple environment variables may be separated by whitespace or spread
870across multiple
871.Cm SendEnv
872directives.
873The default is not to send any environment variables.
874.Pp
875See
876.Sx PATTERNS
877for more information on patterns.
878.It Cm ServerAliveCountMax
879Sets the number of server alive messages (see below) which may be
880sent without
881.Xr ssh 1
882receiving any messages back from the server.
883If this threshold is reached while server alive messages are being sent,
884ssh will disconnect from the server, terminating the session.
885It is important to note that the use of server alive messages is very
886different from
887.Cm TCPKeepAlive
888(below).
889The server alive messages are sent through the encrypted channel
890and therefore will not be spoofable.
891The TCP keepalive option enabled by
892.Cm TCPKeepAlive
893is spoofable.
894The server alive mechanism is valuable when the client or
895server depend on knowing when a connection has become inactive.
896.Pp
897The default value is 3.
898If, for example,
899.Cm ServerAliveInterval
900(see below) is set to 15 and
901.Cm ServerAliveCountMax
902is left at the default, if the server becomes unresponsive,
903ssh will disconnect after approximately 45 seconds.
904This option applies to protocol version 2 only.
905.It Cm ServerAliveInterval
906Sets a timeout interval in seconds after which if no data has been received
907from the server,
908.Xr ssh 1
909will send a message through the encrypted
910channel to request a response from the server.
911The default
912is 0, indicating that these messages will not be sent to the server.
913This option applies to protocol version 2 only.
914.It Cm SmartcardDevice
915Specifies which smartcard device to use.
916The argument to this keyword is the device
917.Xr ssh 1
918should use to communicate with a smartcard used for storing the user's
919private RSA key.
920By default, no device is specified and smartcard support is not activated.
921.It Cm StrictHostKeyChecking
922If this flag is set to
923.Dq yes ,
924.Xr ssh 1
925will never automatically add host keys to the
926.Pa ~/.ssh/known_hosts
927file, and refuses to connect to hosts whose host key has changed.
928This provides maximum protection against trojan horse attacks,
929though it can be annoying when the
930.Pa /etc/ssh/ssh_known_hosts
931file is poorly maintained or when connections to new hosts are
932frequently made.
933This option forces the user to manually
934add all new hosts.
935If this flag is set to
936.Dq no ,
937ssh will automatically add new host keys to the
938user known hosts files.
939If this flag is set to
940.Dq ask ,
941new host keys
942will be added to the user known host files only after the user
943has confirmed that is what they really want to do, and
944ssh will refuse to connect to hosts whose host key has changed.
945The host keys of
946known hosts will be verified automatically in all cases.
947The argument must be
948.Dq yes ,
949.Dq no ,
950or
951.Dq ask .
952The default is
953.Dq ask .
954.It Cm TCPKeepAlive
955Specifies whether the system should send TCP keepalive messages to the
956other side.
957If they are sent, death of the connection or crash of one
958of the machines will be properly noticed.
959However, this means that
960connections will die if the route is down temporarily, and some people
961find it annoying.
962.Pp
963The default is
964.Dq yes
965(to send TCP keepalive messages), and the client will notice
966if the network goes down or the remote host dies.
967This is important in scripts, and many users want it too.
968.Pp
969To disable TCP keepalive messages, the value should be set to
970.Dq no .
971.It Cm Tunnel
972Request
973.Xr tun 4
974device forwarding between the client and the server.
975The argument must be
976.Dq yes ,
977.Dq point-to-point
978(layer 3),
979.Dq ethernet
980(layer 2),
981or
982.Dq no .
983Specifying
984.Dq yes
985requests the default tunnel mode, which is
986.Dq point-to-point .
987The default is
988.Dq no .
989.It Cm TunnelDevice
990Specifies the
991.Xr tun 4
992devices to open on the client
993.Pq Ar local_tun
994and the server
995.Pq Ar remote_tun .
996.Pp
997The argument must be
998.Sm off
999.Ar local_tun Op : Ar remote_tun .
1000.Sm on
1001The devices may be specified by numerical ID or the keyword
1002.Dq any ,
1003which uses the next available tunnel device.
1004If
1005.Ar remote_tun
1006is not specified, it defaults to
1007.Dq any .
1008The default is
1009.Dq any:any .
1010.It Cm UsePrivilegedPort
1011Specifies whether to use a privileged port for outgoing connections.
1012The argument must be
1013.Dq yes
1014or
1015.Dq no .
1016The default is
1017.Dq no .
1018If set to
1019.Dq yes ,
1020.Xr ssh 1
1021must be setuid root.
1022Note that this option must be set to
1023.Dq yes
1024for
1025.Cm RhostsRSAAuthentication
1026with older servers.
1027.It Cm User
1028Specifies the user to log in as.
1029This can be useful when a different user name is used on different machines.
1030This saves the trouble of
1031having to remember to give the user name on the command line.
1032.It Cm UserKnownHostsFile
1033Specifies a file to use for the user
1034host key database instead of
1035.Pa ~/.ssh/known_hosts .
1036.It Cm VerifyHostKeyDNS
1037Specifies whether to verify the remote key using DNS and SSHFP resource
1038records.
1039If this option is set to
1040.Dq yes ,
1041the client will implicitly trust keys that match a secure fingerprint
1042from DNS.
1043Insecure fingerprints will be handled as if this option was set to
1044.Dq ask .
1045If this option is set to
1046.Dq ask ,
1047information on fingerprint match will be displayed, but the user will still
1048need to confirm new host keys according to the
1049.Cm StrictHostKeyChecking
1050option.
1051The argument must be
1052.Dq yes ,
1053.Dq no ,
1054or
1055.Dq ask .
1056The default is
1057.Dq no .
1058Note that this option applies to protocol version 2 only.
1059.Pp
1060See also
1061.Sx VERIFYING HOST KEYS
1062in
1063.Xr ssh 1 .
1064.It Cm XAuthLocation
1065Specifies the full pathname of the
1066.Xr xauth 1
1067program.
1068The default is
1069.Pa /usr/X11R6/bin/xauth .
1070.El
1071.Sh PATTERNS
1072A
1073.Em pattern
1074consists of zero or more non-whitespace characters,
1075.Sq *
1076(a wildcard that matches zero or more characters),
1077or
1078.Sq ?\&
1079(a wildcard that matches exactly one character).
1080For example, to specify a set of declarations for any host in the
1081.Dq .co.uk
1082set of domains,
1083the following pattern could be used:
1084.Pp
1085.Dl Host *.co.uk
1086.Pp
1087The following pattern
1088would match any host in the 192.168.0.[0-9] network range:
1089.Pp
1090.Dl Host 192.168.0.?
1091.Pp
1092A
1093.Em pattern-list
1094is a comma-separated list of patterns.
1095Patterns within pattern-lists may be negated
1096by preceding them with an exclamation mark
1097.Pq Sq !\& .
1098For example,
1099to allow a key to be used from anywhere within an organisation
1100except from the
1101.Dq dialup
1102pool,
1103the following entry (in authorized_keys) could be used:
1104.Pp
1105.Dl from=\&"!*.dialup.example.com,*.example.com\&"
1106.Sh FILES
1107.Bl -tag -width Ds
1108.It Pa ~/.ssh/config
1109This is the per-user configuration file.
1110The format of this file is described above.
1111This file is used by the SSH client.
1112Because of the potential for abuse, this file must have strict permissions:
1113read/write for the user, and not accessible by others.
1114.It Pa /etc/ssh/ssh_config
1115Systemwide configuration file.
1116This file provides defaults for those
1117values that are not specified in the user's configuration file, and
1118for those users who do not have a configuration file.
1119This file must be world-readable.
1120.El
1121.Sh SEE ALSO
1122.Xr ssh 1
1123.Sh AUTHORS
1124OpenSSH is a derivative of the original and free
1125ssh 1.2.12 release by Tatu Ylonen.
1126Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
1127Theo de Raadt and Dug Song
1128removed many bugs, re-added newer features and
1129created OpenSSH.
1130Markus Friedl contributed the support for SSH
1131protocol versions 1.5 and 2.0.
This page took 0.047209 seconds and 5 git commands to generate.