From owner-freebsd-current Mon Mar 6 13:15:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 0B34337C07D; Mon, 6 Mar 2000 13:15:34 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.10.0.Beta12/8.10.0.Beta12) id e26LFEq68238; Mon, 6 Mar 2000 13:15:14 -0800 (PST) Message-Id: <200003062115.e26LFEq68238@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: David Malone Cc: Warner Losh , Kris Kennaway , bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <20000306210349.A73029@walton.maths.tcd.ie> References: <200003062032.NAA61484@harmony.village.org> <20000306210349.A73029@walton.maths.tcd.ie> Comments: In-reply-to David Malone message dated "Mon, 06 Mar 2000 21:03:50 +0000." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1751912798P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 06 Mar 2000 13:15:14 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_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