From owner-freebsd-stable Sat Oct 14 15:39:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id AD5DE37B66E for ; Sat, 14 Oct 2000 15:39:56 -0700 (PDT) Received: (from kris@localhost) by citusc17.usc.edu (8.9.3/8.9.3) id PAA13999; Sat, 14 Oct 2000 15:41:31 -0700 (PDT) Date: Sat, 14 Oct 2000 15:41:31 -0700 From: Kris Kennaway To: Glen Gross Cc: "'Vivek Khera'" , "stable@FreeBSD.ORG" Subject: Re: turning off rcmd is premature Message-ID: <20001014154131.E13848@citusc17.usc.edu> References: <01C0351A.45CBF470.ggross@symark.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01C0351A.45CBF470.ggross@symark.com>; from ggross@symark.com on Fri, Oct 13, 2000 at 01:34:11PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 13, 2000 at 01:34:11PM -0700, Glen Gross wrote: > >From a non-programmer's standpoint, I also agree that turning off rshd is > premature. The strength of UNIX is traditionally in the fact that it is an > open system. > Excessive zeal to make it secure also makes it less functional, and this is a > delicate balance. Many people will just consider the OS "broken" > if basic functionality is not there. This kind of thing will probably just No basic functionality has been lost. The r* family of commands are still there, they still work as before, and they are still appropriate for some environments (e.g. Kerberos). Removing 1 character from inetd.conf and typing "kill -HUP `cat /var/run/inetd.pid`" is all thats required to enable a service again for your system, if you're one of those people who need or want to use one of them. Thats not a big task. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message