From owner-freebsd-security  Tue Feb  2 16:10:39 1999
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA03777
          for freebsd-security-outgoing; Tue, 2 Feb 1999 16:10:39 -0800 (PST)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03748
          for <freebsd-security@FreeBSD.ORG>; Tue, 2 Feb 1999 16:10:26 -0800 (PST)
          (envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.9.2/8.9.2) with ESMTP id TAA32136;
	Tue, 2 Feb 1999 19:10:12 -0500 (EST)
	(envelope-from matt@zigg.com)
Date: Tue, 2 Feb 1999 19:10:11 -0500 (EST)
From: Matt Behrens <matt@zigg.com>
To: Binh Nguyen <Binh@asu.edu>
cc: freebsd-security@FreeBSD.ORG
Subject: Re: hosts.allow and deny!
In-Reply-To: <Pine.GSO.3.96.990202112911.8764A-100000@ai.asu.edu>
Message-ID: <Pine.BSF.4.05.9902021909430.32126-100000@megaweapon.zigg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

You need the TCP wrappers package.  See /usr/ports/security/tcp_wrapper.

On Tue, 2 Feb 1999, Binh Nguyen wrote:

: Hi!
: 	
: 	I want to ask a question.  Is there a way on Freebsd2.2.8 that I could
: implement the hosts.allow and hosts.deny, so no one could access my server
: without being addin the hosts.allow.
: 	Also, is there a good admin tool for system security such ask monitors
: the system, or any tools that help on how to do hosts.allow and hosts.deny.
: 	Thanks
: 
: Binh Nguyen

- Matt Behrens <matt@zigg.com>
  Network Administrator, zigg.com <http://www.zigg.com/>
  Engineer, Nameless IRC Network <http://www.nameless.net/>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message