Date: Mon, 2 Jun 2003 10:34:06 +0700 (ICT) From: Olivier Nicole <on@cs.ait.ac.th> Cc: freebsd-questions@freebsd.org Subject: Re: Changes to hosts.allow do no affect to inetd daemons some times Message-ID: <200306020334.KAA16838@banyan.cs.ait.ac.th> In-Reply-To: <20030602051705.T16654-100000@amour.ath.cx> (message from Alexander on Mon, 2 Jun 2003 05:26:15 %2B0200 (CEST)) References: <20030602051705.T16654-100000@amour.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
> Sometimes when I change my /etc/hosts.allow and kill and start again > inetd, there is no difference. It's like I haven't edited > /etc/hosts.allow. If I continue making changes and stop/start inetd there > are no affections to the inetd daemons, they allow or deny as > /etc/hosts.allow isn't modified since inetd was first started after the > system bootstrapped. My guess would be that some of the servers started with inetd are still up-and running. Remember that tcpwrapper will filter connection initiated through inetd. If, say, your ftp server is runing and handling requests, it will not be affected by your changes in hosts.allow. Your FTP server does not know that tcpwrapper is ther actually. So at same time you kill -HUp inetd, you should also kill all the services started by inetd and that are running. SSH does access tcpwrapper by itself, so it is not affected by this behaviour. Bests, olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306020334.KAA16838>