[Bug 2627] Documentation update: semantic of ClientAliveCountMax 0 unclear

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Wed Jun 22 18:57:31 AEST 2022


James Dingwall <james.dingwall at ncr.com> changed:

           What    |Removed                     |Added
                 CC|                            |james.dingwall at ncr.com

--- Comment #5 from James Dingwall <james.dingwall at ncr.com> ---
As per comment#4 after an upgrade from Ubuntu 18.04 to Ubuntu 20.04 the
ClientAlive* settings no longer functioned as expected.  My personal
opinion is that the existing behaviour (disconnect with no probes)
could have been clarified in the man page but actually changing
behaviour that existing configurations depended on was not the correct
decision.  It is also unclear what advantage the new behaviour of
ClientAliveCountMax=0 brings, if you don't want the client connection
to be killed then don't configure the parameters, the default
ClientAliveInterval=0 already meant that these messages would not be

Perhaps if you want a client alive message to be sent then
ClientAliveCountMax=-1 could have indicated no disconnect.

cross reference:

You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

More information about the openssh-bugs mailing list