https://bugzilla.mindrot.org/show_bug.cgi?id=3182
Damien Miller <djm@mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org
--- Comment #1 from Damien Miller <djm@mindrot.org> ---
Killing the connection because of inactivity was never the specified
function of ClientAliveInterval and that it happened to work that way
was an accident. Note that the previous behaviour was not reliable - a
client that set a ServerAliveInterval or that kept a forwarded TCP
connection open would never be killed for inactivity.
If you need a idle timeout, then I suggest looking at shell features
(e.g. bash's TMOUT) or something like a PAM module.
--
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
Damien Miller <djm@mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org
--- Comment #1 from Damien Miller <djm@mindrot.org> ---
Killing the connection because of inactivity was never the specified
function of ClientAliveInterval and that it happened to work that way
was an accident. Note that the previous behaviour was not reliable - a
client that set a ServerAliveInterval or that kept a forwarded TCP
connection open would never be killed for inactivity.
If you need a idle timeout, then I suggest looking at shell features
(e.g. bash's TMOUT) or something like a PAM module.
--
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