openssh bugs - Sep 2017 - [Bug 2781] New: ssh tunnel doesn't close after logout

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

            Bug ID: 2781
           Summary: ssh tunnel doesn't close after logout
           Product: Portable OpenSSH
           Version: 7.2p2
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: jg at jguk.org

I noticed that an SSH tunnel won't close until I exit Chrome Browser
that was using the tunnel. Shouldn't ssh force close of the connection?


$ ssh -i "jonny3.pem" -C -D localhost:8080 ubuntu at mypc
Last login: Mon Sep 18 07:25:43 2017 from xx.xx.xx.xx
ubuntu at mypc:~$


>From my desktop:
$ /usr/bin/google-chrome --user-data-dir="$HOME/chrome-with-proxy"
--proxy-server="socks5://localhost:8080"


Try to terminate the ssh connection, and it won't

ubuntu at mypc:~$ logout

<wait 10 seconds>

<close Chrome>

Connection to x.x.x.x closed.

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

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

Darren Tucker <dtucker at zip.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dtucker at zip.com.au

--- Comment #1 from Darren Tucker <dtucker at zip.com.au> ---
(In reply to jg from comment #0)
> I noticed that an SSH tunnel won't close until I exit Chrome Browser
> that was using the tunnel. Shouldn't ssh force close of the
> connection?
No.  In SSH2 the connection and the login are distinct things.
> Try to terminate the ssh connection, and it won't
> ubuntu at mypc:~$ logout
No, you're terminating the interactive shell's channel, which is one of
possibly many channels within the connection.  If you really want to
kill the connection regardless of how many channels are open then use
the ~. escape sequence.

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

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

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |djm at mindrot.org
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Damien Miller <djm at mindrot.org> ---
As Darren mentioned, this is by design.

-- 
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=2781

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #3 from Damien Miller <djm at mindrot.org> ---
closing resolved bugs as of 8.6p1 release

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