Skip to main content
Unix & Linux

Return to Answer

Commonmark migration
Source Link
Community Bot
Community Bot
  • 1

I think You disabled the configuration by setting ClientAliveCountMax to 0. So setting it to 1 should do the job.

ClientAliveCountMax

 

Sets the number of client alive messages which may be sent without sshd(8) receiving any messages back from the client. If this threshold is reached while client alive messages are being sent, sshd will disconnect the client, terminating the session. It is important to note that the use of client alive messages is very different from TCPKeepAlive. The client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive.

 

The default value is 3. If ClientAliveInterval is set to 15, and ClientAliveCountMax is left at the default, unresponsive SSH clients will be disconnected after approximately 45 seconds.

But I have to admit I agree with @TienPhan. It's better to keep the configuration off the server. Still it depends on the use case. If all users should be handled the same way, server side configuration is the option.

I think You disabled the configuration by setting ClientAliveCountMax to 0. So setting it to 1 should do the job.

ClientAliveCountMax

 

Sets the number of client alive messages which may be sent without sshd(8) receiving any messages back from the client. If this threshold is reached while client alive messages are being sent, sshd will disconnect the client, terminating the session. It is important to note that the use of client alive messages is very different from TCPKeepAlive. The client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive.

 

The default value is 3. If ClientAliveInterval is set to 15, and ClientAliveCountMax is left at the default, unresponsive SSH clients will be disconnected after approximately 45 seconds.

But I have to admit I agree with @TienPhan. It's better to keep the configuration off the server. Still it depends on the use case. If all users should be handled the same way, server side configuration is the option.

I think You disabled the configuration by setting ClientAliveCountMax to 0. So setting it to 1 should do the job.

ClientAliveCountMax

Sets the number of client alive messages which may be sent without sshd(8) receiving any messages back from the client. If this threshold is reached while client alive messages are being sent, sshd will disconnect the client, terminating the session. It is important to note that the use of client alive messages is very different from TCPKeepAlive. The client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive.

The default value is 3. If ClientAliveInterval is set to 15, and ClientAliveCountMax is left at the default, unresponsive SSH clients will be disconnected after approximately 45 seconds.

But I have to admit I agree with @TienPhan. It's better to keep the configuration off the server. Still it depends on the use case. If all users should be handled the same way, server side configuration is the option.

Source Link
Jakub Jindra
Jakub Jindra
  • 1.5k
  • 1
  • 14
  • 26

I think You disabled the configuration by setting ClientAliveCountMax to 0. So setting it to 1 should do the job.

ClientAliveCountMax

Sets the number of client alive messages which may be sent without sshd(8) receiving any messages back from the client. If this threshold is reached while client alive messages are being sent, sshd will disconnect the client, terminating the session. It is important to note that the use of client alive messages is very different from TCPKeepAlive. The client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive.

The default value is 3. If ClientAliveInterval is set to 15, and ClientAliveCountMax is left at the default, unresponsive SSH clients will be disconnected after approximately 45 seconds.

But I have to admit I agree with @TienPhan. It's better to keep the configuration off the server. Still it depends on the use case. If all users should be handled the same way, server side configuration is the option.