summaryrefslogtreecommitdiff
path: root/ssh_config.5
diff options
context:
space:
mode:
Diffstat (limited to 'ssh_config.5')
-rw-r--r--ssh_config.536
1 files changed, 34 insertions, 2 deletions
diff --git a/ssh_config.5 b/ssh_config.5
index 210da059b..25485f3da 100644
--- a/ssh_config.5
+++ b/ssh_config.5
@@ -127,8 +127,15 @@ Valid arguments are
127If set to 127If set to
128.Dq yes , 128.Dq yes ,
129passphrase/password querying will be disabled. 129passphrase/password querying will be disabled.
130In addition, the
131.Cm ServerAliveInterval
132and
133.Cm SetupTimeOut
134options will both be set to 300 seconds by default.
130This option is useful in scripts and other batch jobs where no user 135This option is useful in scripts and other batch jobs where no user
131is present to supply the password. 136is present to supply the password,
137and where it is desirable to detect a
138broken network swiftly.
132The argument must be 139The argument must be
133.Dq yes 140.Dq yes
134or 141or
@@ -559,7 +566,10 @@ from the server,
559will send a message through the encrypted 566will send a message through the encrypted
560channel to request a response from the server. 567channel to request a response from the server.
561The default 568The default
562is 0, indicating that these messages will not be sent to the server. 569is 0, indicating that these messages will not be sent to the server,
570or 300 if the
571.Cm BatchMode
572option is set.
563This option applies to protocol version 2 only. 573This option applies to protocol version 2 only.
564.It Cm ServerAliveCountMax 574.It Cm ServerAliveCountMax
565Sets the number of server alive messages (see above) which may be 575Sets the number of server alive messages (see above) which may be
@@ -588,6 +598,22 @@ If, for example,
588.Cm ServerAliveCountMax 598.Cm ServerAliveCountMax
589is left at the default, if the server becomes unresponsive ssh 599is left at the default, if the server becomes unresponsive ssh
590will disconnect after approximately 45 seconds. 600will disconnect after approximately 45 seconds.
601.It Cm SetupTimeOut
602Normally,
603.Nm ssh
604blocks indefinitely whilst waiting to receive the ssh banner and other
605setup protocol from the server, during the session setup.
606This can cause
607.Nm ssh
608to hang under certain circumstances.
609If this option is set,
610.Nm ssh
611will give up if no data from the server is received for the specified
612number of seconds.
613The argument must be an integer.
614The default is 0 (disabled), or 300 if
615.Cm BatchMode
616is set.
591.It Cm SmartcardDevice 617.It Cm SmartcardDevice
592Specifies which smartcard device to use. 618Specifies which smartcard device to use.
593The argument to this keyword is the device 619The argument to this keyword is the device
@@ -635,6 +661,12 @@ Specifies whether the system should send TCP keepalive messages to the
635other side. 661other side.
636If they are sent, death of the connection or crash of one 662If they are sent, death of the connection or crash of one
637of the machines will be properly noticed. 663of the machines will be properly noticed.
664This option only uses TCP keepalives (as opposed to using ssh level
665keepalives), so takes a long time to notice when the connection dies.
666As such, you probably want
667the
668.Cm ServerAliveInterval
669option as well.
638However, this means that 670However, this means that
639connections will die if the route is down temporarily, and some people 671connections will die if the route is down temporarily, and some people
640find it annoying. 672find it annoying.