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