From owner-freebsd-security Mon Sep 14 18:12:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02389 for freebsd-security-outgoing; Mon, 14 Sep 1998 18:12:10 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from roble.com (roble.com [207.5.40.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02379 for ; Mon, 14 Sep 1998 18:12:06 -0700 (PDT) (envelope-from sendmail@roble.com) Received: from localhost (localhost [127.0.0.1]) by roble.com (Roble) with SMTP id SAA29862 for ; Mon, 14 Sep 1998 18:11:45 -0700 (PDT) Date: Mon, 14 Sep 1998 18:11:45 -0700 (PDT) From: Roger Marquis To: freebsd-security@FreeBSD.ORG Subject: Re: sshd In-Reply-To: <35FD82A8.84601D49@dal.net> 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 Mon, 14 Sep 1998, Studded wrote: > Foolish consistency is the hobgoblin of small minds. I am also in the > camp of those who disable inetd almost universally, and run sshd > standalone. Since I don't think either camp is going to convince the > other, perhaps we should let this drop? Au contraire, consistency is fundamental to good systems administration. KISS and consistency are what keeps the Macintosh alive despite all odds. KISS, consistency and efficiency are what keeps sites with dozens or hundreds of Unix boxes running with high uptime and a small staff. If you don't need inetd then it's probably a good idea to disable it and run all your daemons all the time however most hosts, including firewalls, do use it. Is there a significant security (or other) reason to disable it? Roger Marquis Roble Systems Consulting http://www.roble.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message