Date: Tue, 25 Jun 2002 20:10:54 +1200 (NZST) From: Andrew McNaughton <andrew@scoop.co.nz> To: "Matthew N. Dodd" <winter@jurai.net> Cc: Darren Reed <avalon@coombs.anu.edu.au>, <security@FreeBSD.ORG> Subject: Re: Time to look put more resources into FreeSSH ? Message-ID: <20020625200524.O69343-100000@a2> In-Reply-To: <20020625035702.F95270-100000@sasami.jurai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 25 Jun 2002, Matthew N. Dodd wrote: > On Tue, 25 Jun 2002, Darren Reed wrote: > > > 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 agree with this. I set NO_OPENSSH and NO_OPENSSL in my /etc/make.conf and use ports. Apart from being able to upgrade independently of the system, I like having the /usr/local/etc/rc.d scripts on hand. Why doesn't FreeBSD make these scripts exist in a stand alone form for things that get installed with the system? Is there a philosophy behind it, or is it just historical? Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020625200524.O69343-100000>