From owner-freebsd-hackers Sat Jul 8 13:47:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id F194537BB1D; Sat, 8 Jul 2000 13:47:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA51439; Sat, 8 Jul 2000 13:47:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 8 Jul 2000 13:47:56 -0700 (PDT) From: Kris Kennaway To: Adrian Filipi-Martin Cc: Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: OpenSSH 2.X problem with escape chars? In-Reply-To: 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 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