Date: Sat, 8 Jul 2000 19:26:17 -0500 From: Steve Ames <steve@virtual-voodoo.com> To: Kris Kennaway <kris@FreeBSD.org> Cc: Adrian Filipi-Martin <adrian@ubergeeks.com>, freebsd-hackers@FreeBSD.org Subject: Re: OpenSSH 2.X problem with escape chars? Message-ID: <20000708192617.A84753@virtual-voodoo.com> In-Reply-To: <Pine.BSF.4.21.0007081346440.50712-100000@freefall.freebsd.org>; from kris@FreeBSD.org on Sat, Jul 08, 2000 at 01:47:56PM -0700 References: <Pine.BSF.4.10.10007081421030.29764-100000@lorax.ubergeeks.com> <Pine.BSF.4.21.0007081346440.50712-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <forsythe@alum.mit.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000708192617.A84753>