From owner-freebsd-security Tue Jun 25 1: 2:32 2002 Delivered-To: freebsd-security@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 49C5537B4B5 for ; Tue, 25 Jun 2002 00:59:48 -0700 (PDT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.2/8.12.2) with ESMTP id g5P7xg2A075471; Tue, 25 Jun 2002 03:59:43 -0400 (EDT) (envelope-from winter@jurai.net) Date: Tue, 25 Jun 2002 03:59:42 -0400 (EDT) From: "Matthew N. Dodd" To: Darren Reed Cc: security@FreeBSD.ORG Subject: Re: Time to look put more resources into FreeSSH ? In-Reply-To: <200206250632.QAA02400@caligula.anu.edu.au> Message-ID: <20020625035702.F95270-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 25 Jun 2002, Darren Reed wrote: > I think the subject raises the question well enough. > > What do others think about creating a little "bio-diversity" and > moving from OpenSSH to FreeSSH at some point in the future as the > "default" ssh installed ? If it moves the ssh utility out of the system so that the upgrade path is via ports rather than build/install world then I'm for it. Having OpenSSH in the source tree doesn't buy us anything over having it in ports and managing our local patches in the projects/ CVS hierarchy. I see no problem with having a set of 'default packages' installed by sysinstall. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message