openssh bugs - Jan 2018 - [Bug 2830] New: Add option to set TCP_USER_TIMEOUT on linux

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

            Bug ID: 2830
           Summary: Add option to set TCP_USER_TIMEOUT on linux
           Product: Portable OpenSSH
           Version: 7.6p1
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: sshd
          Assignee: unassigned-bugs at mindrot.org
          Reporter: wallior at gmail.com

Created attachment 3118
  --> https://bugzilla.mindrot.org/attachment.cgi?id=3118&action=edit
Adds support for TCP_USER_TIMEOUT.

Since 2010, Linux has had a socket option to be able to set a custom
timeout of how long a TCP session can stay up if the link drops
(default is ~15 set by tcp_retries1/2).
https://patchwork.ozlabs.org/patch/62889/

The attached patch lets the user set the TCP_USER_TIMEOUT on both sshd
and ssh.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

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

Darren Tucker <dtucker at dtucker.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dtucker at dtucker.net
   Attachment #3118|0                           |1
           is patch|                            |
   Attachment #3118|application/octet-stream    |text/plain
          mime type|                            |

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

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

--- Comment #1 from Darren Tucker <dtucker at dtucker.net> ---
I don't think we want to add support for a platform-specific socket
option like this.

On the client side you can implement it as an external ProxyCommand
dialer that sets the option and passes the connected socket back via
ProxyUseFdpass.

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

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

--- Comment #2 from wallior at gmail.com ---
> On the client side you can implement it as an external ProxyCommand
> dialer that sets the option and passes the connected socket back via
> ProxyUseFdpass.
I see how this will work on the client side. This socket option needs
to be set on the server side too. Any suggestion how to do that?

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

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

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |djm at mindrot.org

--- Comment #3 from Damien Miller <djm at mindrot.org> ---
Isn't this use-case already handled by
ClientAliveInterval/ClientAliveCountMax and the corresponding client
option? These allow termination of connections for all kinds of network
interruptions, not just link drops.

-- 
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.