Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 06 Mar 2000 13:15:14 -0800
From:      bmah@CA.Sandia.GOV (Bruce A. Mah)
To:        David Malone <dwmalone@maths.tcd.ie>
Cc:        Warner Losh <imp@village.org>, 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:  <200003062115.e26LFEq68238@nimitz.ca.sandia.gov>
In-Reply-To: <20000306210349.A73029@walton.maths.tcd.ie> 
References:  <Pine.BSF.4.21.0003061226190.39179-100000@hub.freebsd.org> <200003062032.NAA61484@harmony.village.org> <20000306210349.A73029@walton.maths.tcd.ie>

next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1751912798P
Content-Type: text/plain; charset=us-ascii

If memory serves me right, David Malone wrote:
> 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 actua
> l
> > : 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.

Rather than let the users guess at various incompatabilities (imagined 
and real), why not give them a few examples, as in your (David's) last 
message?

"Care needs to be taken when converting from ssh to OpenSSH.  OpenSSH's
command-line parsing isn't 100% compatible with ssh, some of the default
options have been changed, some options (such as AllowHosts) have been
removed, and it produces a few more warning messages than ssh."

Bruce.




--==_Exmh_1751912798P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: eGz8t7RAhR1hLdezOH4kUK6TAAlKdk46

iQA/AwUBOMQf4tjKMXFboFLDEQJxewCgpDjLUDw5STEZKecVJA42gg2NGZoAoM85
j1+jqyF/TgdRSEMQwd1JHMAx
=8+8A
-----END PGP SIGNATURE-----

--==_Exmh_1751912798P--


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?200003062115.e26LFEq68238>