Date: Wed, 13 Oct 1999 12:28:04 +0930 (CST) From: Greg Lewis <glewis@trc.adelaide.edu.au> To: freebsd-security@freebsd.org Subject: Re: FreeSSH Message-ID: <199910130258.MAA62519@ares.maths.adelaide.edu.au> In-Reply-To: <Pine.BSF.4.10.9910121304420.89607-100000@hub.freebsd.org> from Kris Kennaway at "Oct 12, 1999 01:06:50 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> I've been keeping an eye on it - once it stabilizes a bit I might have a > go porting it - it shouldn't be too hard. It would probably be as a port, > though, unless we get broad consensus it should go into the src tree > (*cough* *cough*, unlikely :). > > Kris Thats good to hear Kris! I'm curious on why you believe it would be hard to get a broad consensus though. Remote login capability is something that is clearly desired (cf. telnet and rlogin being enabled in the standard install). If there is an appropriately licensed much more secure version of this functionality available then it would seem a good idea to have it in the base install too (although probably starting as being off by default except if you twiddle an rc.conf knob). Obviously with that argument there would be some other things go in, so thats not enough by itself if you want to avoid bloat. However, I'm guessing that a lot of sysadmins install ssh as their first act on a new install. Maybe when this reaches _most_ sysadmins it would be a candidate for the base system? Do folks have any thoughts on whether most people do/should install ssh? In the interests of minimising bloat we could balance its inclusion by deleting something like, say, uucp. (:-) for the uucps users) -- Greg Lewis glewis@trc.adelaide.edu.au Computing Officer +61 8 8303 5083 Teletraffic Research Centre 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?199910130258.MAA62519>