Bug 1301

Summary:	Repeated ~. need an intervening ENTER to be effective
Product:	Portable OpenSSH	Reporter:	Felix Finch <felix>
Component:	ssh	Assignee:	Assigned to nobody <unassigned-bugs>
Status:	CLOSED WORKSFORME
Severity:	normal
Priority:	P4
Version:	4.5p1
Hardware:	ix86
OS:	Linux

Description Felix Finch 2007-03-30 03:05:50 AEST

ssh from a to b.

ssh from b to c.

Use "~~." to exit from c back to b.

Now "~." on b results in "command not recognized" by bash.

A second "~." will exit from b back to a.

Any intervening command on b, even ENTER alone, does the trick.

This could be a bug in bash for all I know, but my hunch is ssh.  

In this particular case, "a" is an rPath x86 machine, version OpenSSH_4.5p1, OpenSSL 0.9.7f 22 Mar 2005.  "b" is a gentoo x86, version 
OpenSSH_4.5p1, OpenSSL 0.9.8e 23 Feb 2007.  "c" is "a" again.

Comment 1 Damien Miller 2007-03-30 10:48:28 AEST

I don't think this is a bug; it is a consequence of chained SSH connections and is logically consistent behaviour. 

Even if we were to consider it a bug, it would be near impossible to fix in the general case because a SSH session has no robust way of knowing that another SSH session is being tunneled through it.

Comment 2 Damien Miller 2008-04-04 09:58:59 AEDT

Close resolved bugs after release.