From owner-freebsd-current Mon Mar 6 13:50:34 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A68FE37BD1A; Mon, 6 Mar 2000 13:50:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A3C392E815C; Mon, 6 Mar 2000 13:50:30 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 13:50:30 -0800 (PST) From: Kris Kennaway To: David Malone Cc: Warner Losh , bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <20000306210349.A73029@walton.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, David Malone wrote: > 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. None of these affect the operation of OpenSSH in your network. Sure, you have to check the config files when you migrate to it, but the point is it's not incompatible with other SSH implementations, and we don't want to scare people into thinking it has weird lurking bugs and they'd better not use it. 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-current" in the body of the message