openssh bugs - Mar 2007 - [Bug 1301] Repeated ~. need an intervening ENTER to be effective

http://bugzilla.mindrot.org/show_bug.cgi?id=1301

           Summary: Repeated ~. need an intervening ENTER to be effective
           Product: Portable OpenSSH
           Version: 4.5p1
          Platform: ix86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P4
         Component: ssh
        AssignedTo: bitbucket at mindrot.org
        ReportedBy: felix at crowfix.com


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.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1301


djm at mindrot.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Comment #1 from djm at mindrot.org  2007-03-30 10:48 -------
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.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.