From owner-freebsd-questions Wed Apr 9 05:19:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA15921 for questions-outgoing; Wed, 9 Apr 1997 05:19:22 -0700 (PDT) Received: from nexis.net (customer-1.ican.net [198.133.36.101]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA15906 for ; Wed, 9 Apr 1997 05:19:20 -0700 (PDT) Received: from localhost (james@localhost) by nexis.net (8.8.5/8.8.5) with SMTP id IAA01587 for ; Wed, 9 Apr 1997 08:17:47 -0400 (EDT) Date: Wed, 9 Apr 1997 08:17:47 -0400 (EDT) From: James FitzGibbon To: freebsd-questions@freebsd.org Subject: Compiling ypserv with tcp wrappers ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What is required to compile ypserv with tcp wrapper support ? Is it just to define TCP_WRAPPER while compiling ? I've tried this; it completes successfully. I didn't notice any -lwrap commands in the make output though. I would think that in order to use functions from the TCP wrappers library, one would have to link libwrap.a or libwrap.so, wouldn't they ? Using this switch seems only to centralize your host access into the same file as the rest of your TCP wrapper-protected service; it doesn't seem to do the forward/reverse DNS checks that TCP wrappers are primarily used for. Has anyone hacked this into ypserv ? Would it not make ypserv even more secure for use on a 'public' wire ? -- j.