From owner-freebsd-current Mon Mar 6 14:53: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7153937BAA8; Mon, 6 Mar 2000 14:52:57 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA56002; Mon, 6 Mar 2000 15:52:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA62626; Mon, 6 Mar 2000 15:52:40 -0700 (MST) Message-Id: <200003062252.PAA62626@harmony.village.org> To: Kris Kennaway Subject: Re: ssh strangeness in -current... Cc: bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 12:29:01 PST." References: Date: Mon, 06 Mar 2000 15:52:39 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this any better? I've removed the emotionally charged compatibility word. 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 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, available options and default 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. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message