[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openssh-bugs
Subject:    [Bug 2627] New: Documentation update: semantic of ClientAliveCountMax 0 unclear
From:       bugzilla-daemon () bugzilla ! mindrot ! org
Date:       2016-10-20 17:44:56
Message-ID: bug-2627-705 () https ! bugzilla ! mindrot ! org/
[Download RAW message or body]

https://bugzilla.mindrot.org/show_bug.cgi?id=2627

            Bug ID: 2627
           Summary: Documentation update: semantic of ClientAliveCountMax
                    0 unclear
           Product: Portable OpenSSH
           Version: 7.3p1
          Hardware: All
                OS: All
            Status: NEW
          Severity: trivial
          Priority: P5
         Component: sshd
          Assignee: unassigned-bugs@mindrot.org
          Reporter: woody.weaver@comcast.net

It seems to be reasonably well understood (e.g.
https://lists.mindrot.org/pipermail/openssh-unix-dev/2013-November/031781.html)
that setting ClientAliveCountMax to 0 can terminate an alive but idle
session.  However, this is not clear, as demonstrated by that email.

It would be helpful to add something like

>With ClientAliveCountMax == 0 there will be no "client alive packet"
>sent and I will force a disconnection if there is no traffic within
>ClientAliveInterval secs.

to the section on ClientAliveCountMax or ClientAliveInterval.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[prev in list] [next in list] [prev in thread] [next in thread]