]> andersk Git - openssh.git/blame - ssh_config.5
- (djm) Return of the dreaded PAM_TTY_KLUDGE, which went missing in
[openssh.git] / ssh_config.5
CommitLineData
588df31a 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.\"
09ab3296 37.\" $OpenBSD: ssh_config.5,v 1.9 2003/05/15 14:55:25 djm Exp $
588df31a 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 $HOME/.ssh/config
47.It Pa /etc/ssh/ssh_config
48.El
49.Sh DESCRIPTION
50.Nm ssh
51obtains configuration data from the following sources in
52the following order:
4dcbbeea 53.Bl -enum -offset indent -compact
54.It
55command-line options
56.It
57user's configuration file
58.Pq Pa $HOME/.ssh/config
59.It
60system-wide configuration file
61.Pq Pa /etc/ssh/ssh_config
62.El
588df31a 63.Pp
64For each parameter, the first obtained value
65will be used.
66The configuration files contain sections bracketed by
67.Dq Host
68specifications, and that section is only applied for hosts that
69match one of the patterns given in the specification.
70The matched host name is the one given on the command line.
71.Pp
72Since the first obtained value for each parameter is used, more
73host-specific declarations should be given near the beginning of the
74file, and general defaults at the end.
75.Pp
76The configuration file has the following format:
77.Pp
78Empty lines and lines starting with
79.Ql #
80are comments.
81.Pp
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.
95.Pp
96The possible
97keywords and their meanings are as follows (note that
98keywords are case-insensitive and arguments are case-sensitive):
99.Bl -tag -width Ds
100.It Cm Host
101Restricts the following declarations (up to the next
102.Cm Host
103keyword) to be only for those hosts that match one of the patterns
104given after the keyword.
105.Ql \&*
106and
107.Ql ?
108can be used as wildcards in the
109patterns.
110A single
111.Ql \&*
112as a pattern can be used to provide global
113defaults for all hosts.
114The host is the
115.Ar hostname
116argument given on the command line (i.e., the name is not converted to
117a canonicalized host name before matching).
118.It Cm AFSTokenPassing
119Specifies whether to pass AFS tokens to remote host.
120The argument to this keyword must be
121.Dq yes
122or
123.Dq no .
124This option applies to protocol version 1 only.
125.It Cm BatchMode
126If set to
127.Dq yes ,
128passphrase/password querying will be disabled.
129This option is useful in scripts and other batch jobs where no user
130is present to supply the password.
131The argument must be
132.Dq yes
133or
134.Dq no .
135The default is
136.Dq no .
137.It Cm BindAddress
138Specify the interface to transmit from on machines with multiple
139interfaces or aliased addresses.
140Note that this option does not work if
141.Cm UsePrivilegedPort
142is set to
143.Dq yes .
144.It Cm ChallengeResponseAuthentication
145Specifies whether to use challenge response authentication.
146The argument to this keyword must be
147.Dq yes
148or
149.Dq no .
150The default is
151.Dq yes .
152.It Cm CheckHostIP
153If this flag is set to
154.Dq yes ,
155ssh will additionally check the host IP address in the
156.Pa known_hosts
157file.
158This allows ssh to detect if a host key changed due to DNS spoofing.
159If the option is set to
160.Dq no ,
161the check will not be executed.
162The default is
163.Dq yes .
164.It Cm Cipher
165Specifies the cipher to use for encrypting the session
166in protocol version 1.
167Currently,
168.Dq blowfish ,
169.Dq 3des ,
170and
171.Dq des
172are supported.
173.Ar des
174is only supported in the
175.Nm ssh
176client for interoperability with legacy protocol 1 implementations
177that do not support the
178.Ar 3des
a4e5acef 179cipher.
180Its use is strongly discouraged due to cryptographic weaknesses.
588df31a 181The default is
182.Dq 3des .
183.It Cm Ciphers
184Specifies the ciphers allowed for protocol version 2
185in order of preference.
186Multiple ciphers must be comma-separated.
187The default is
188.Pp
189.Bd -literal
190 ``aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
191 aes192-cbc,aes256-cbc''
192.Ed
193.It Cm ClearAllForwardings
194Specifies that all local, remote and dynamic port forwardings
195specified in the configuration files or on the command line be
a4e5acef 196cleared.
197This option is primarily useful when used from the
588df31a 198.Nm ssh
199command line to clear port forwardings set in
200configuration files, and is automatically set by
201.Xr scp 1
202and
203.Xr sftp 1 .
204The argument must be
205.Dq yes
206or
207.Dq no .
208The default is
209.Dq no .
210.It Cm Compression
211Specifies whether to use compression.
212The argument must be
213.Dq yes
214or
215.Dq no .
216The default is
217.Dq no .
218.It Cm CompressionLevel
219Specifies the compression level to use if compression is enabled.
220The argument must be an integer from 1 (fast) to 9 (slow, best).
221The default level is 6, which is good for most applications.
222The meaning of the values is the same as in
223.Xr gzip 1 .
224Note that this option applies to protocol version 1 only.
225.It Cm ConnectionAttempts
226Specifies the number of tries (one per second) to make before exiting.
227The argument must be an integer.
228This may be useful in scripts if the connection sometimes fails.
229The default is 1.
09ab3296 230.It Cm ConnectTimeout
231Specifies the timeout (in seconds) used when connecting to the ssh
232server, instead of using the default system TCP timeout. This value is
233used only when the target is down or really unreachable, not when it
234refuses the connection.
588df31a 235.It Cm DynamicForward
236Specifies that a TCP/IP port on the local machine be forwarded
237over the secure channel, and the application
238protocol is then used to determine where to connect to from the
a4e5acef 239remote machine.
240The argument must be a port number.
588df31a 241Currently the SOCKS4 protocol is supported, and
242.Nm ssh
243will act as a SOCKS4 server.
244Multiple forwardings may be specified, and
a4e5acef 245additional forwardings can be given on the command line.
246Only the superuser can forward privileged ports.
588df31a 247.It Cm EscapeChar
248Sets the escape character (default:
249.Ql ~ ) .
250The escape character can also
251be set on the command line.
252The argument should be a single character,
253.Ql ^
254followed by a letter, or
255.Dq none
256to disable the escape
257character entirely (making the connection transparent for binary
258data).
259.It Cm ForwardAgent
260Specifies whether the connection to the authentication agent (if any)
261will be forwarded to the remote machine.
262The argument must be
263.Dq yes
264or
265.Dq no .
266The default is
267.Dq no .
dbcdea68 268.Pp
a4e5acef 269Agent forwarding should be enabled with caution.
270Users with the ability to bypass file permissions on the remote host
271(for the agent's Unix-domain socket)
272can access the local agent through the forwarded connection.
273An attacker cannot obtain key material from the agent,
dbcdea68 274however they can perform operations on the keys that enable them to
275authenticate using the identities loaded into the agent.
588df31a 276.It Cm ForwardX11
277Specifies whether X11 connections will be automatically redirected
278over the secure channel and
279.Ev DISPLAY
280set.
281The argument must be
282.Dq yes
283or
284.Dq no .
285The default is
286.Dq no .
dbcdea68 287.Pp
a4e5acef 288X11 forwarding should be enabled with caution.
289Users with the ability to bypass file permissions on the remote host
290(for the user's X authorization database)
291can access the local X11 display through the forwarded connection.
292An attacker may then be able to perform activities such as keystroke monitoring.
588df31a 293.It Cm GatewayPorts
294Specifies whether remote hosts are allowed to connect to local
295forwarded ports.
296By default,
297.Nm ssh
a4e5acef 298binds local port forwardings to the loopback address.
299This prevents other remote hosts from connecting to forwarded ports.
588df31a 300.Cm GatewayPorts
301can be used to specify that
302.Nm ssh
303should bind local port forwardings to the wildcard address,
304thus allowing remote hosts to connect to forwarded ports.
305The argument must be
306.Dq yes
307or
308.Dq no .
309The default is
310.Dq no .
311.It Cm GlobalKnownHostsFile
312Specifies a file to use for the global
313host key database instead of
314.Pa /etc/ssh/ssh_known_hosts .
315.It Cm HostbasedAuthentication
316Specifies whether to try rhosts based authentication with public key
317authentication.
318The argument must be
319.Dq yes
320or
321.Dq no .
322The default is
323.Dq no .
324This option applies to protocol version 2 only and
325is similar to
326.Cm RhostsRSAAuthentication .
327.It Cm HostKeyAlgorithms
328Specifies the protocol version 2 host key algorithms
329that the client wants to use in order of preference.
330The default for this option is:
331.Dq ssh-rsa,ssh-dss .
332.It Cm HostKeyAlias
333Specifies an alias that should be used instead of the
334real host name when looking up or saving the host key
335in the host key database files.
336This option is useful for tunneling ssh connections
337or for multiple servers running on a single host.
338.It Cm HostName
339Specifies the real host name to log into.
340This can be used to specify nicknames or abbreviations for hosts.
341Default is the name given on the command line.
342Numeric IP addresses are also permitted (both on the command line and in
343.Cm HostName
344specifications).
345.It Cm IdentityFile
346Specifies a file from which the user's RSA or DSA authentication identity
347is read. The default is
348.Pa $HOME/.ssh/identity
349for protocol version 1, and
350.Pa $HOME/.ssh/id_rsa
351and
352.Pa $HOME/.ssh/id_dsa
353for protocol version 2.
354Additionally, any identities represented by the authentication agent
355will be used for authentication.
356The file name may use the tilde
357syntax to refer to a user's home directory.
358It is possible to have
359multiple identity files specified in configuration files; all these
360identities will be tried in sequence.
361.It Cm KeepAlive
362Specifies whether the system should send TCP keepalive messages to the
363other side.
364If they are sent, death of the connection or crash of one
365of the machines will be properly noticed.
366However, this means that
367connections will die if the route is down temporarily, and some people
368find it annoying.
369.Pp
370The default is
371.Dq yes
372(to send keepalives), and the client will notice
373if the network goes down or the remote host dies.
374This is important in scripts, and many users want it too.
375.Pp
376To disable keepalives, the value should be set to
377.Dq no .
378.It Cm KerberosAuthentication
379Specifies whether Kerberos authentication will be used.
380The argument to this keyword must be
381.Dq yes
382or
383.Dq no .
384.It Cm KerberosTgtPassing
385Specifies whether a Kerberos TGT will be forwarded to the server.
386This will only work if the Kerberos server is actually an AFS kaserver.
387The argument to this keyword must be
388.Dq yes
389or
390.Dq no .
391.It Cm LocalForward
392Specifies that a TCP/IP port on the local machine be forwarded over
393the secure channel to the specified host and port from the remote machine.
394The first argument must be a port number, and the second must be
395.Ar host:port .
396IPv6 addresses can be specified with an alternative syntax:
397.Ar host/port .
398Multiple forwardings may be specified, and additional
399forwardings can be given on the command line.
400Only the superuser can forward privileged ports.
401.It Cm LogLevel
402Gives the verbosity level that is used when logging messages from
403.Nm ssh .
404The possible values are:
405QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2 and DEBUG3.
a4e5acef 406The default is INFO.
407DEBUG and DEBUG1 are equivalent.
408DEBUG2 and DEBUG3 each specify higher levels of verbose output.
588df31a 409.It Cm MACs
410Specifies the MAC (message authentication code) algorithms
411in order of preference.
412The MAC algorithm is used in protocol version 2
413for data integrity protection.
414Multiple algorithms must be comma-separated.
415The default is
416.Dq hmac-md5,hmac-sha1,hmac-ripemd160,hmac-sha1-96,hmac-md5-96 .
417.It Cm NoHostAuthenticationForLocalhost
418This option can be used if the home directory is shared across machines.
419In this case localhost will refer to a different machine on each of
420the machines and the user will get many warnings about changed host keys.
421However, this option disables host authentication for localhost.
422The argument to this keyword must be
423.Dq yes
424or
425.Dq no .
426The default is to check the host key for localhost.
427.It Cm NumberOfPasswordPrompts
428Specifies the number of password prompts before giving up.
429The argument to this keyword must be an integer.
430Default is 3.
431.It Cm PasswordAuthentication
432Specifies whether to use password authentication.
433The argument to this keyword must be
434.Dq yes
435or
436.Dq no .
437The default is
438.Dq yes .
439.It Cm Port
440Specifies the port number to connect on the remote host.
441Default is 22.
442.It Cm PreferredAuthentications
443Specifies the order in which the client should try protocol 2
444authentication methods. This allows a client to prefer one method (e.g.
445.Cm keyboard-interactive )
446over another method (e.g.
447.Cm password )
448The default for this option is:
449.Dq hostbased,publickey,keyboard-interactive,password .
450.It Cm Protocol
451Specifies the protocol versions
452.Nm ssh
453should support in order of preference.
454The possible values are
455.Dq 1
456and
457.Dq 2 .
458Multiple versions must be comma-separated.
459The default is
460.Dq 2,1 .
461This means that
462.Nm ssh
463tries version 2 and falls back to version 1
464if version 2 is not available.
465.It Cm ProxyCommand
466Specifies the command to use to connect to the server.
467The command
468string extends to the end of the line, and is executed with
469.Pa /bin/sh .
470In the command string,
471.Ql %h
472will be substituted by the host name to
473connect and
474.Ql %p
475by the port.
476The command can be basically anything,
477and should read from its standard input and write to its standard output.
478It should eventually connect an
479.Xr sshd 8
480server running on some machine, or execute
481.Ic sshd -i
482somewhere.
483Host key management will be done using the
484HostName of the host being connected (defaulting to the name typed by
485the user).
a4e5acef 486Setting the command to
487.Dq none
f78bde70 488disables this option entirely.
588df31a 489Note that
490.Cm CheckHostIP
491is not available for connects with a proxy command.
492.Pp
493.It Cm PubkeyAuthentication
494Specifies whether to try public key authentication.
495The argument to this keyword must be
496.Dq yes
497or
498.Dq no .
499The default is
500.Dq yes .
501This option applies to protocol version 2 only.
502.It Cm RemoteForward
503Specifies that a TCP/IP port on the remote machine be forwarded over
504the secure channel to the specified host and port from the local machine.
505The first argument must be a port number, and the second must be
506.Ar host:port .
507IPv6 addresses can be specified with an alternative syntax:
508.Ar host/port .
509Multiple forwardings may be specified, and additional
510forwardings can be given on the command line.
511Only the superuser can forward privileged ports.
512.It Cm RhostsAuthentication
513Specifies whether to try rhosts based authentication.
514Note that this
515declaration only affects the client side and has no effect whatsoever
516on security.
517Most servers do not permit RhostsAuthentication because it
518is not secure (see
519.Cm RhostsRSAAuthentication ) .
520The argument to this keyword must be
521.Dq yes
522or
523.Dq no .
524The default is
525.Dq no .
878b8992 526This option applies to protocol version 1 only and requires
527.Nm ssh
528to be setuid root and
529.Cm UsePrivilegedPort
530to be set to
531.Dq yes .
588df31a 532.It Cm RhostsRSAAuthentication
533Specifies whether to try rhosts based authentication with RSA host
534authentication.
535The argument must be
536.Dq yes
537or
538.Dq no .
539The default is
540.Dq no .
541This option applies to protocol version 1 only and requires
542.Nm ssh
543to be setuid root.
544.It Cm RSAAuthentication
545Specifies whether to try RSA authentication.
546The argument to this keyword must be
547.Dq yes
548or
549.Dq no .
550RSA authentication will only be
551attempted if the identity file exists, or an authentication agent is
552running.
553The default is
554.Dq yes .
555Note that this option applies to protocol version 1 only.
556.It Cm SmartcardDevice
557Specifies which smartcard device to use. The argument to this keyword is
558the device
559.Nm ssh
560should use to communicate with a smartcard used for storing the user's
561private RSA key. By default, no device is specified and smartcard support
562is not activated.
563.It Cm StrictHostKeyChecking
564If this flag is set to
565.Dq yes ,
566.Nm ssh
567will never automatically add host keys to the
568.Pa $HOME/.ssh/known_hosts
569file, and refuses to connect to hosts whose host key has changed.
570This provides maximum protection against trojan horse attacks,
571however, can be annoying when the
572.Pa /etc/ssh/ssh_known_hosts
573file is poorly maintained, or connections to new hosts are
574frequently made.
575This option forces the user to manually
576add all new hosts.
577If this flag is set to
578.Dq no ,
579.Nm ssh
580will automatically add new host keys to the
581user known hosts files.
582If this flag is set to
583.Dq ask ,
584new host keys
585will be added to the user known host files only after the user
586has confirmed that is what they really want to do, and
587.Nm ssh
588will refuse to connect to hosts whose host key has changed.
589The host keys of
590known hosts will be verified automatically in all cases.
591The argument must be
592.Dq yes ,
593.Dq no
594or
595.Dq ask .
596The default is
597.Dq ask .
598.It Cm UsePrivilegedPort
599Specifies whether to use a privileged port for outgoing connections.
600The argument must be
601.Dq yes
602or
603.Dq no .
604The default is
605.Dq no .
878b8992 606If set to
607.Dq yes
608.Nm ssh
609must be setuid root.
588df31a 610Note that this option must be set to
611.Dq yes
612if
613.Cm RhostsAuthentication
614and
615.Cm RhostsRSAAuthentication
616authentications are needed with older servers.
617.It Cm User
618Specifies the user to log in as.
619This can be useful when a different user name is used on different machines.
620This saves the trouble of
621having to remember to give the user name on the command line.
622.It Cm UserKnownHostsFile
623Specifies a file to use for the user
624host key database instead of
625.Pa $HOME/.ssh/known_hosts .
21289cd0 626.It Cm VerifyHostKeyDNS
627Specifies whether to verify the remote key using DNS and SSHFP resource
628records.
629The default is
630.Dq no .
588df31a 631.It Cm XAuthLocation
57ff5eeb 632Specifies the full pathname of the
588df31a 633.Xr xauth 1
634program.
635The default is
636.Pa /usr/X11R6/bin/xauth .
637.El
638.Sh FILES
639.Bl -tag -width Ds
640.It Pa $HOME/.ssh/config
641This is the per-user configuration file.
642The format of this file is described above.
643This file is used by the
644.Nm ssh
645client.
646This file does not usually contain any sensitive information,
647but the recommended permissions are read/write for the user, and not
648accessible by others.
649.It Pa /etc/ssh/ssh_config
650Systemwide configuration file.
651This file provides defaults for those
652values that are not specified in the user's configuration file, and
653for those users who do not have a configuration file.
654This file must be world-readable.
655.El
656.Sh AUTHORS
657OpenSSH is a derivative of the original and free
658ssh 1.2.12 release by Tatu Ylonen.
659Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
660Theo de Raadt and Dug Song
661removed many bugs, re-added newer features and
662created OpenSSH.
663Markus Friedl contributed the support for SSH
664protocol versions 1.5 and 2.0.
665.Sh SEE ALSO
666.Xr ssh 1
This page took 2.858316 seconds and 5 git commands to generate.