Bug 1331 - ControlClient escape sequences non-functional
Summary: ControlClient escape sequences non-functional
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: 4.6p1
Hardware: Other Linux
: P2 normal
Assignee: Damien Miller
URL:
Keywords:
: 1484 (view as bug list)
Depends on:
Blocks: V_5_1
  Show dependency tree / graph
 
Reported: 2007-07-06 01:28 AEST by David Woodhouse
Modified: 2010-06-05 02:12 AEST (History)
1 user (show)

See Also:

Attachments
Process escapes from multiplex slave sessions (15.46 KB, patch)
2008-06-12 11:41 AEST, Damien Miller 		no flags Details | Diff
patch (347 bytes, patch)
2010-06-05 02:12 AEST, David Woodhouse 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Woodhouse 2007-07-06 01:28:07 AEST 
When using the OpenSSH client in ControlClient mode, escape sequences (such as ~. to kill the connection) are not functional.
Comment 1 Damien Miller 2008-06-12 11:41:23 AEST 
Created attachment 1512 [details]
Process escapes from multiplex slave sessions

This hooks up the escape filter to multiplex slave sessions and makes the escape state per-session.
Comment 2 Damien Miller 2008-06-12 13:43:57 AEST 
patch applied, this will be in openssh-5.2 (barring regressions)
Comment 3 Damien Miller 2008-07-09 22:35:45 AEST 
*** Bug 1484 has been marked as a duplicate of this bug. ***
Comment 4 Damien Miller 2008-07-22 12:19:06 AEST 
Mass update RESOLVED->CLOSED after release of openssh-5.1
Comment 5 David Woodhouse 2010-06-04 20:11:52 AEST 
Doesn't seem to be working for me in 5.5p1 on Linux. If I send ~. to a multiplex slave session, it just locks up and stops working. Other escape sequences seem to work though.
Comment 6 David Woodhouse 2010-06-05 02:12:48 AEST 
Created attachment 1854 [details]
patch

This "fixes" it, although I'm far from sure that it's the correct fix... it does serve to highlight the issue though.

The client never exits because the control socket never gets closed from the master side.