[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-bugs
Subject:    [icbmx2@yahoo.com: Re: conf/11950: /etc/hosts.allow confuses tcp wrapper]
From:       Matthew Hunt <mph () astro ! caltech ! edu>
Date:       1999-05-31 0:30:03
[Download RAW message or body]

The following reply was made to PR conf/11950; it has been noted by GNATS.

From: Matthew Hunt <mph@astro.caltech.edu>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: [icbmx2@yahoo.com: Re: conf/11950: /etc/hosts.allow confuses tcp wrapper]
Date: Sun, 30 May 1999 17:22:24 -0700

 ----- Forwarded message from An <icbmx2@yahoo.com> -----
 
 Date: Sun, 30 May 1999 17:18:53 -0700 (PDT)
 From: An <icbmx2@yahoo.com>
 Reply-To: icbmx2@yahoo.com
 Subject: Re: conf/11950: /etc/hosts.allow confuses tcp wrapper
 To: Matthew Hunt <mph@phobos.caltech.edu>
 
 Hi,
 
 I don't remember how /etc/hosts.allow got to /etc. I
 am not sure if it was installed with 3.2-R. If not,
 then I  edited one there (some man pages still point
 to /etc/hosts.allow).
 
 What happens when you have the file in /etc, is that
 tcpd doesn't correctly interpret the rules. For
 example, having the line:
 
 telnetd: ALL: allow 
 
 is not honored. What's more, variables like %a don't
 get correctly replaced. Delete /etc/hosts.allow and
 only have /usr/local/etc/hosts.allow and everything is
 ok.
 
 Also tcpdchk doesn't detect
 /usr/local/etc/hosts.allow. It appears to read from
 /etc/hosts.allow, and interprets the fields wrong (it
 doesn't follow the extended format???).
 
 ----- End forwarded message -----
 


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


[prev in list] [next in list] [prev in thread] [next in thread]