From owner-freebsd-security Wed Oct 13 3:17:24 1999 Delivered-To: freebsd-security@freebsd.org Received: from pogo.caustic.org (pogo.caustic.org [216.69.69.123]) by hub.freebsd.org (Postfix) with ESMTP id AA8B614E47 for ; Wed, 13 Oct 1999 03:17:20 -0700 (PDT) (envelope-from jan@caustic.org) Received: from localhost (jan@localhost) by pogo.caustic.org (8.9.3/ignatz) with ESMTP id DAA95821; Wed, 13 Oct 1999 03:17:43 -0700 (PDT) Date: Wed, 13 Oct 1999 03:17:43 -0700 (PDT) From: "f.johan.beisser" To: Greg Lewis Cc: freebsd-security@FreeBSD.ORG Subject: Re: FreeSSH In-Reply-To: <199910130258.MAA62519@ares.maths.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 13 Oct 1999, Greg Lewis wrote: > Do folks have any thoughts on whether most people do/should install ssh? just about everyone i know does use ssh. i encourage it, VERY heavily, and have started the road at my work to using it almost exclusivly in place of telnet, rlogon, etc. we don't use SSH2 tho, even though the tools would be handy to have (sftp, as an example). for us, it's the first thing that gets installed. doesn't matter what platform it is, there is an SSH client on the machine. > In the interests of minimising bloat we could balance its inclusion by > deleting something like, say, uucp. > (:-) for the uucps users) actually, i don't think this is a good idea. there are still a few (very few.. i hope) networks and LAN's that use UUCP for mail transfer and such. in keeping FreeBSD as portable and usable by as many users as posable, it would.. well, screw them over. -- jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message