From owner-freebsd-hackers Sat Jul 8 17:26:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 1FD6E37B50C; Sat, 8 Jul 2000 17:26:19 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.11.0.Beta3/8.11.0.Beta3) id e690QIQ90971; Sat, 8 Jul 2000 19:26:18 -0500 (EST) Date: Sat, 8 Jul 2000 19:26:17 -0500 From: Steve Ames To: Kris Kennaway Cc: Adrian Filipi-Martin , freebsd-hackers@FreeBSD.org Subject: Re: OpenSSH 2.X problem with escape chars? Message-ID: <20000708192617.A84753@virtual-voodoo.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from kris@FreeBSD.org on Sat, Jul 08, 2000 at 01:47:56PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just forwarded my original message to 'openssh@openssh.com'. -Steve On Sat, Jul 08, 2000 at 01:47:56PM -0700, Kris Kennaway wrote: > On Sat, 8 Jul 2000, Adrian Filipi-Martin wrote: > > > 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. > > You should report this to the OpenSSH guys: see www.openssh.com for list > of mailing lists. It doesn't sound like a bug we've introduced in our > version, and if it's a generic OpenSSH bug then it should be fixed at the > source. > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message