From owner-freebsd-current Mon Mar 6 14:57:57 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 33D1E37BB41; Mon, 6 Mar 2000 14:57:55 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 31CBF2E8110; Mon, 6 Mar 2000 14:57:55 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 14:57:55 -0800 (PST) From: Kris Kennaway To: Warner Losh Cc: bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <200003062252.PAA62626@harmony.village.org> 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, Warner Losh wrote: > Is this any better? I've removed the emotionally charged > compatibility word. Some more picking :) > 20000225: > OpenSSH has been added to FreeBSD. This may conflict with the > ports/security/ssh port since it installs binaries into > /usr/bin and the port goes into /usr/local/bin. Most paths > have /usr/bin in the path before /usr/local/bin, so problems > may arrise. If you don't want OpenSSH, add NO_OPENSSH=yes to arise :) > your make.conf. > > You will also need to enable openssh in /etc/rc.conf if you OpenSSH > want to run the new servers. You may need to move your key host key > and other config files from /usr/local/etc to /etc/ssh. > > Openssh's command line parsing, available options and default OpenSSH > settings aren't the same as ssh, so some care needs to be > taken in its operation. One should do a full audit of all > configuration settings. Apart from those small nits I think it's fine. 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