From owner-freebsd-security  Tue Feb  2 15:54:57 1999
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA29598
          for freebsd-security-outgoing; Tue, 2 Feb 1999 15:54:57 -0800 (PST)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from cs.bc.edu (cs.bc.edu [136.167.32.100])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29582
          for <freebsd-security@FreeBSD.ORG>; Tue, 2 Feb 1999 15:54:53 -0800 (PST)
          (envelope-from kelleyry@cs.bc.edu)
Received: from localhost (kelleyry@localhost)
	by cs.bc.edu (8.8.6/8.8.6) with ESMTP id SAA24861;
	Tue, 2 Feb 1999 18:56:23 -0500 (EST)
Date: Tue, 2 Feb 1999 18:56:21 -0500 (EST)
From: Ryan Kelley <kelleyry@cs.bc.edu>
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.OSF.4.05.9902021854100.8579-100000@cs.bc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

	check out /usr/ports/security/tcp_wrapper. you also might want to
check out /etc/login.access which gives you decent control over user
logins both locally and remotely. latez.
	-ryan

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
> 
> 
> 
> 
> 
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message



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