From owner-freebsd-ports  Tue Aug  5 18:41:42 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA18647
          for ports-outgoing; Tue, 5 Aug 1997 18:41:42 -0700 (PDT)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA18641;
          Tue, 5 Aug 1997 18:41:27 -0700 (PDT)
Received: from localhost (jfieber@localhost)
	by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id UAA09688;
	Tue, 5 Aug 1997 20:40:21 -0500 (EST)
Date: Tue, 5 Aug 1997 20:40:21 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Satoshi Asami <asami@cs.berkeley.edu>
cc: mark@grondar.za, jkh@time.cdrom.com, torstenb@FreeBSD.ORG,
        ports@FreeBSD.ORG
Subject: Re: Major bogon in tcp_wrappers port.
In-Reply-To: <199708052332.QAA07103@vader.cs.berkeley.edu>
Message-ID: <Pine.BSF.3.96.970805203711.17562h-100000@fallout.campusview.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 5 Aug 1997, Satoshi Asami wrote:

> (Asbestos suit removed)
> 
>  * _*PRETTY_PLEASE*_ cant we bring this into the "core" FreeBSD?
>  * 
>  * With all the squeling about security, IMHO it is silly not to.
> 
> I have no problem with the general principle stated above.  I don't
> know anything about the actual working of tcp_wrapper, so I'll refrain 
> from commenting on this specific case.

I just installed it and it appears to be basically transparent
unless you set up a hosts.allow and/or hosts.deny file---similar
to the login.access functionality of login.  It does send more
stuff about connections to syslog, but with the default
syslog.conf, I don't think any of it actually gets recorded.

-john