ssh disconnect escape sequence doesn't work on a broken multiplexed connection

Bug #1193620 reported by Olathe
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openssh (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I use the following SSH configuration options:
  ControlMaster auto
  ControlPath ~/.ssh/.socket-%r@%h:%p
  ControlPersist 60

It looks as if it's configured correctly because opening multiple connections using the same username and host-port combination shares the first connection.

[Enter], [~], [.] closes each session individually, which is great. However, that disconnect escape sequence appears to do absolutely nothing if the multiplexed connection dies abnormally (for instance, if my WiFi connection dies), which is the time when I most need the disconnect sequence to work, since I'm not going to be doing much on that dead session anymore, and I'd like to restart it.

[Enter], [~], [.] works fine on a *nonmultiplexed* connection when it dies abnormally.

======

$ lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04

$ apt-cache policy openssh-client
openssh-client:
  Installed: 1:6.1p1-4
  Candidate: 1:6.1p1-4
  Version table:
 *** 1:6.1p1-4 0
        500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: openssh-client 1:6.1p1-4
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Sat Jun 22 09:01:57 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-04-04 (78 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
RelatedPackageVersions:
 ssh-askpass N/A
 libpam-ssh N/A
 keychain N/A
 ssh-askpass-gnome N/A
SSHClientVersion: OpenSSH_6.1p1 Debian-4, OpenSSL 1.0.1c 10 May 2012
SourcePackage: openssh
UpgradeStatus: Upgraded to raring on 2013-05-25 (27 days ago)

Revision history for this message
Olathe (erlercw+launchpad) wrote :
Changed in openssh (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Olathe (erlercw+launchpad) wrote :

An imperfect workaround is to add the following line to the configuration:
  ServerAliveInterval 15

The client then automatically closes the connection after 3 failed connectivity checks in a row. The checks are done every 15 seconds.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openssh (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.