Re: [Bacula-users] hosts.allow issues

[Dan L. <da...@la...>]

On Thu, 30 Oct 2003, Phil Stracchino wrote:

> On Thu, Oct 30, 2003 at 05:50:44PM -0500, Dan Langille wrote:
> > Did your telnet get a "not welcome" message?  If not, then
> > /etc/hosts.allow is not set according to the test conditions.
> >
> > Also, I did not mention, and this point is important, you must
> > restart bacula-fd before the test.  Any previous invocations of
> > hosts_access alter the test results.  I have no idea why.
>
>
> OK, I just retested as follows:
>
>
> (1) Stop bacula.
>
> (2) Write /etc/hosts.allow as follows:
>
> ALL : ALL \
>          : severity auth.info \
>          : twist /bin/echo "You are not welcome to use %d from %h."
>
> #ALL:		local
> #ALL:		192.168.0.0/255.255.255.0
> portmap:	192.168.0.0/255.255.255.0
> gdm:		192.168.0.0/255.255.255.0
>
> (3) Restart bacula
>
> (4) ssh to minbar
>
> (5)
> minbar:root:~:1 # telnet babylon5 9102
> Trying 192.168.0.10...
> Connected to babylon5.babcom.com.
> Escape character is '^]'.
> ^]
> telnet> quit
> Connection to babylon5.babcom.com closed.
> minbar:root:~:2 #
>
>
> However, a sudden thought occurs to me.  Last time I knew, although the
> --with-tcpwrappers option existed in bacula configuration, it did not
> work.  Has this changed?  Do I need to rebuild with tcpwrappers enabled
> for this to work?

Yes, I forgot that bit.  Bacula needs to have tcpwrapper support.  The
configure args is --with-tcp-wrappers.