2 ms·
Resumption? None that I can find in sshd_config but there are several related to increasing tolerances to prevent it from terminating in the first place. Clien
by cmurf 9y ago
Resumption? None that I can find in sshd_config but there are several related to increasing tolerances to prevent it from terminating in the first place.
ClientAliveCountMax default is 3
ClientAliveInterval default is 0
Ergo by default ClientAlive messaging isn't used. If Interval were set to 60, the connection would be terminated after 3 minutes.
From man sshd_config:
TCPKeepAlive
"Specifies whether the system should send TCP keepalive messages to the other side. If they are sent, death of the connection or crash of one of the machines will be properly noticed. However, this means that connections will die if the route is down temporarily, and some people find it annoying. On the other hand, if TCP keepalives are not sent, sessions may hang indefinitely on the server, leaving "ghost" users and consuming server resources.
The default is yes (to send TCP keepalive messages), and the server will notice if the network goes down or the client host crashes. This avoids infinitely hanging sessions."
That's probably not that interesting because it's considered spoofable. Maybe more interesting are the client side ssh_config options which allow for opportunistic multiplexing:
ControlMaster
ControlPath
ControlPersist