From owner-freebsd-doc@FreeBSD.ORG Thu Oct 14 13:52:22 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C3FB16A4CE; Thu, 14 Oct 2004 13:52:22 +0000 (GMT) Received: from volginfo.ru (ns.volginfo.ru [217.23.84.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id A317043D3F; Thu, 14 Oct 2004 13:52:21 +0000 (GMT) (envelope-from den@FreeBSD.org) Received: from FreeBSD.org (llp-13.vistcom.ru [217.23.84.68]) by volginfo.ru (Postfix) with ESMTP id 75F2C2010; Thu, 14 Oct 2004 17:52:24 +0400 (MSD) Message-ID: <416E8491.8080500@FreeBSD.org> Date: Thu, 14 Oct 2004 17:52:17 +0400 From: Denis Peplin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040205 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Tom Rhodes References: <416E4DFD.3040203@FreeBSD.org> <20041014102459.GD799@zaphod.nitro.dk> <20041014092213.22d6914d@localhost> In-Reply-To: <20041014092213.22d6914d@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-doc@FreeBSD.org cc: "Simon L. Nielsen" Subject: Re: TCP Wrappers section (handbook/security): services is not daemons X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 13:52:22 -0000 Hello! Yes, i see now that using word "daemon" for services is tradition here :) It will not be a big problem, if we will add short description for this "term" (explain tradition) in beginning of the section. Tom Rhodes wrote: > On Thu, 14 Oct 2004 12:24:59 +0200 > "Simon L. Nielsen" wrote: > > >>On 2004.10.14 13:59:25 +0400, Denis Peplin wrote: >> >>["s/daemons/services/g" in TCP Wrappers section] >> >>>Please, look at patch attached. >> >>Personally I don't care much either way, but hosts_access(5) at least >>refers to the server programs as "daemons". Snip from host_access(5): >> >> daemon_list : client_list [ : shell_command ] >> >> daemon_list is a list of one or more daemon process names (argv[0] val- >> ues) or wildcards (see below). > > > I won't object to the patch; as if being the author gives me > any more right. But I would like to point out that to my knowledge > every book I've seen which discussed tcpwrappers used 'daemon'. > > Think of it this way, a daemon 'qpopper' offers POP3 mail access, > to allow this service you need to add qpopper to hosts.allow. > If you just list pop3, you'll see everything break. > > I consider a daemon a utility/program/whatever the item that > delivers the service we need, as in the example above. Since > I know that I'm not alone in that train of thought, I'll let > you choose. If you say "just add the service" then you'll > break the ACL in TCP Wrappers for every instance that the service > is not the name of the daemon: > > ... > > nevermind, I really can't think of an example other than services > marked 'internal' in inetd.conf; those have no external daemon > associated with them. >