From owner-freebsd-ports  Tue Aug  5 01:33:24 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA29468
          for ports-outgoing; Tue, 5 Aug 1997 01:33:24 -0700 (PDT)
Received: from insl1.etec.uni-karlsruhe.de (uucp@insl1.etec.uni-karlsruhe.de [129.13.109.178])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA29462
          for <ports@freebsd.org>; Tue, 5 Aug 1997 01:33:19 -0700 (PDT)
Received: (from uucp@localhost) by insl1.etec.uni-karlsruhe.de (8.8.6/8.8.2) with UUCP id KAA04737 for ports@freebsd.org; Tue, 5 Aug 1997 10:33:16 +0200 (CEST)
Received: (from erb@localhost) by insl2.etec.uni-karlsruhe.de (8.8.6/8.8.2) id KAA27758; Tue, 5 Aug 1997 10:32:12 +0200 (CEST)
Date: Tue, 5 Aug 1997 10:32:12 +0200 (CEST)
From: Olaf Erb <erb@inss1.etec.uni-karlsruhe.de>
Message-Id: <199708050832.KAA27758@insl2.etec.uni-karlsruhe.de>
To: ports@freebsd.org
Subject: Re: Major bogon in tcp_wrappers port.
Reply-To: erb@inss1.etec.uni-karlsruhe.de
In-Reply-To: <8624.870767928@time.cdrom.com>
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <8624.870767928@time.cdrom.com> you write:
>Yes, I read the man pages for tcpd and for hosts_access(5) and pretty
>much everything I could get my hands on, and no matter what I put in
>for my /etc/hosts.allow and /etc/hosts.deny files, it *always* allowed
>the connection in.  After tearing out a little hair, it finally

Heh ;-) I ran into the same problem one year ago or so.. being used to 
tcp_wrappers for years I put the files into /etc/, too, and have been shocked
by some luser logging in via telnet ;-) Perhaps I should have done a send-pr
this time...

Olaf