From owner-freebsd-current Mon Mar 6 13:48: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 5FC0F37BA03; Mon, 6 Mar 2000 13:47:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D7382E815C; Mon, 6 Mar 2000 13:47:58 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 13:47:58 -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: <200003062032.NAA61484@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: > +20000225: > + OpenSSH has been added to FreeBSD. This may conflict with the > + ssh port since it installs binaries into /usr/bin and the port You probably should refer to the ports by name: /usr/ports/security/ssh and /usr/ports/security/openssh (which is obsoleted by having it in the base) > + 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 arise > + want OpenSSH, add NO_OPENSSH=yes to your make.conf. > + > + You will also need to enable openssh in /etc/rc.conf if you > + want to run the new servers. You may need to move your key > + and other config files from /usr/local/etc to /etc/ssh. > + > + Openssh's command line parsing isn't 100% compatible with ssh, > + so some care needs to be taken in its operation. This is better. 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