https://bugzilla.mindrot.org/show_bug.cgi?id=3172
--- Comment #6 from Damien Miller <djm@mindrot.org> ---
ClientAliveCountMax=0 has never been specified to work as an idle
timeout. If it did that then it was by accident and would be
unreliable. E.g. if the client specified it's own ServerAliveTimeout or
kept a forwarded TCP connection open then it would never fire.
--
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.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
--- Comment #6 from Damien Miller <djm@mindrot.org> ---
ClientAliveCountMax=0 has never been specified to work as an idle
timeout. If it did that then it was by accident and would be
unreliable. E.g. if the client specified it's own ServerAliveTimeout or
kept a forwarded TCP connection open then it would never fire.
--
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.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs