From owner-freebsd-security Thu Jul 1 8:37:56 1999 Delivered-To: freebsd-security@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id CEC8D14A13 for ; Thu, 1 Jul 1999 08:37:32 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10zitc-000Dcf-00; Thu, 01 Jul 1999 17:37:04 +0200 From: Sheldon Hearn To: "Roger Rabbit" Reply-To: freebsd-questions@freebsd.org Cc: freebsd-security@FreeBSD.ORG Subject: Re: tcp wrappers In-reply-to: Your message of "Thu, 01 Jul 1999 17:23:41 +0200." <007701bec3d5$b36d7ce0$2790ccc3@intrafish.no> Date: Thu, 01 Jul 1999 17:37:04 +0200 Message-ID: <52368.930843424@axl.noc.iafrica.com> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 01 Jul 1999 17:23:41 +0200, "Roger Rabbit" wrote: > But I can't see tcpd anywhere, only tcpdcheck and so on. Why is this ? If you look at the inetd manpage, you'll see that it supports builtin wrapping. You don't need tcpd. > What if I want to set up different access rules based on the protocol in = > use, not the program ? That's a limitation of hosts.allow. Short of creating a copy of the daemon binary with a new name, you can't do what you want to with inetd and TCP Wrappers. For information on why you don't have an ld.so for your old AOUT tcpserver program, see the 3.2RELEASE notes: http://www.freebsd.org/releases/3.2R/errata.html If you have further questions on configuration issues, please continue this thread in freebsd-questions, not on the security list. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message