"John J. LeMay Jr." wrote:
>
> ** Reply to message from Sadin Nurkic <[EMAIL PROTECTED]> on Sun, 14
> Jan 2001 15:55:51 +1100
>
> > There must be a different reason why those daemons get killed off because, they
> > are not linked in any way to /etc/hosts.*.
>
> I disagree. The hosts.allow and hosts.deny are exactly what is causing the
> services to fail to respond. I added the "all:local 192.168" to hosts.allow and
> "all:all" to hosts.deny and both swat and ssh stopped working. Changed the
> hosts.allow to "all:all" and both services started working immediately.
>
You'd be correct as SWAT is run from inetd (uses tcpwrappers with
hosts.allow/deny).
You will notice that in the documentation of SAMBA, that SWAT fails to
function if
you use any limitation features available in the smb.conf and I'm
assuming that
the same effects might be felt if the limitation is provided by
tcpwappers too.
As for SSH, it is a stand-alone daemon, but by default does use
hosts.allow/deny.
My recomendation would be to add a line in hosts.allow as: "ssh:all" and
use
sshd_config's options to limit incoming connection interfaces. ("man
sshd" for
details)
Woody ([EMAIL PROTECTED])
---------------------------------------------------------------
Gatewood Green Web Developer
http://www.linux.org/ The first stop for Linux info on the Net
Email: [EMAIL PROTECTED]
---------------------------------------------------------------
All opinions expressed by me are my own and not necessarily
endorsed by Linux Online, Inc. or Linux Headquarters, Inc.
