From owner-freebsd-questions Tue Jul 13 13:40:46 1999 Delivered-To: freebsd-questions@freebsd.org Received: from smtp3.hawaii.rr.com (smtp3.hawaii.rr.com [204.210.97.13]) by hub.freebsd.org (Postfix) with ESMTP id 24AFB14BE4 for ; Tue, 13 Jul 1999 13:40:41 -0700 (PDT) (envelope-from art@hawaii.rr.com) Received: from taz - 24.94.75.210 by smtp3.hawaii.rr.com with Microsoft SMTPSVC(5.5.1774.114.11); Tue, 13 Jul 1999 10:28:58 -1000 Message-Id: <3.0.6.32.19990713104036.030794d0@clients1.hawaii.rr.com> X-Sender: art@clients1.hawaii.rr.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 13 Jul 1999 10:40:36 -1000 To: John Heyer From: "Art Neilson, KH7PZ" Subject: Re: Problems with TCP Wrappers in 3.2 Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is no hosts.deny in FreeBSD 3.2-R. It is all combined in hosts.allow now. The comments at the top of the default hosts.allow state this explicitly. # hosts.allow access control file for "tcp wrapped" apps. # $Id: hosts.allow,v 1.2.2.2 1999/05/11 01:35:01 obrien Exp $ # # NOTE: The hosts.deny file is not longer used. Instead, put both 'allow' # and 'deny' rules in the hosts.allow file. # see hosts_options(5) for the format of this file. # hosts_access(5) no longer fully applies. # This is an example! You will need to modify it for your specific # requirements! I also have the %d problem you describe and was wondering about it as well. At 03:24 PM 7/13/99 -0500, you wrote: > >I'm having some troubles with TCP wrappers in 3.2, and was wondering if >there are any known bugs/patches, etc. My hosts.allow file looks like - >popper : ALL > >Then in hosts.deny - >ALL : ALL EXCEPT ournetwork/mask : twist /bin/echo "acess to %d not allowed" > >Everything works fine - with the exception of pop3 which is wide open, >all other connections are allowed/denied by the IP address range I've >specified. The problem is that after a few day of uptime, TCP wrappers >seems to "break" suddenly. In /var/log/messages, I see things like > >Jul 13 14:44:55 horse inetd[25034]: twist dialup.somewherelse to /bin/echo > >Note that %d is null, and the dialup user who should have access to the >popper is denied. I run "kill -9 `cat /var/run/inetd.pid'; inetd" >and everything's back to normal and working fine. > >We have a similar setup on our web server, which lets ftpd open since we >use an ftpaccess file for security instead. I've observed the problem on >another 3.2 machine was well. Anybody seen this where %d ends up being >null? > >-- >"Your illogical approach ... does have its advantages." > -- Spock, after being Checkmated by Kirk > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > -- __ / ) _/_ It is a capital mistake to theorise before one has data. /--/ __ / Insensibly one begins to twist facts to suit theories, / (_/ (_<__ Instead of theories to suit facts. -- Sherlock Holmes, "A Scandal in Bohemia" Arthur W. Neilson III, KH7PZ Bank of Hawaii Tech Support art@hawaii.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message