Bug 1331

Summary:

ControlClient escape sequences non-functional

Product:

Portable OpenSSH

Reporter:

David Woodhouse <dwmw2>

Component:

ssh

Assignee:

Damien Miller <djm>

Status:

CLOSED FIXED

Severity:

normal

CC:

web

Priority:

Version:

4.6p1

Hardware:

Other

OS:

Linux

Bug Depends on:

Bug Blocks:

1452

Attachments:

Description	Flags
Process escapes from multiplex slave sessions	none
patch	none

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.