Date: Mon, 6 Mar 2000 21:03:50 +0000 From: David Malone <dwmalone@maths.tcd.ie> To: Warner Losh <imp@village.org> Cc: Kris Kennaway <kris@hub.freebsd.org>, bloom@acm.org, John Baldwin <jhb@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... Message-ID: <20000306210349.A73029@walton.maths.tcd.ie> In-Reply-To: <200003062032.NAA61484@harmony.village.org>; from imp@village.org on Mon, Mar 06, 2000 at 01:32:00PM -0700 References: <Pine.BSF.4.21.0003061226190.39179-100000@hub.freebsd.org> <200003062032.NAA61484@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 06, 2000 at 01:32:00PM -0700, Warner Losh wrote: > : > + Openssh isn't 100% compatible with ssh, so some care needs to > : > + be taken in its operation. > : > : This sounds bad. Are you referring to the -o syntax differences, or actual > : incompatabilities? There have been unsubstantiated reports of > : interoperability problems, but nothing well documented here. > > I'm talking about the -o syntax difference specifically. How does the > following sound? [SNIP] > + Openssh's command line parsing isn't 100% compatible with ssh, > + so some care needs to be taken in its operation. I'd leave it saying that it isn't 100% compatible - it may sound bad but it's true. There are several other things that aren't the same: default options are different, some options have been removed (AllowHosts is one that I know of), it produces warning messages where the old ssh wouldn't have. I'm sure there are other differences too. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000306210349.A73029>