From owner-freebsd-hackers Sat Jul 8 11:26: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [209.145.74.241]) by hub.freebsd.org (Postfix) with ESMTP id 1BECB37B9E1 for ; Sat, 8 Jul 2000 11:25:56 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.9.3/8.8.8) with ESMTP id OAA29787; Sat, 8 Jul 2000 14:24:25 -0400 (EDT) (envelope-from adrian@ubergeeks.com) Date: Sat, 8 Jul 2000 14:24:25 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: OpenSSH 2.X problem with escape chars? In-Reply-To: <200007080229.e682Trd77135@virtual-voodoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Jul 2000, Steve Ames wrote: > > Hey... just noticed something odd. I just upgrading one of my FBSD boxes > to the latest -STABLE and modified /etc/ssh/sshd_config to use version > 2 then 1 (Protocol 2,1). After doing this when I connect to that server > the escape sequences (~^Z and friends (as per 'man 1 ssh')) no longer > work. If I connect version 1 they do. If I connect version 2 they don't. > > Any thoughts? The client I'm connecting from is a 5.0-CURRENT (7/6/00) > system. > > -Steve The same problem exists under 4-STABLE from 07/04/00. I haven't had timt to dig into it for real, but running ssh with -v, seemed to make me believe that the client end was pasing along the ~ to the remote end. IIRC, the ~ should be dealt with on the client end. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message