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