[TriLUG] Re: Problems with hosts.deny hosts.allow

[Melissa Evans]

You might want to check and make sure your SSH implementation is limiting
connections, if that is important. OpenSSH, for instance, has to be
explicitly compiled with TCP Wrappers support.

Hi, by the way.  I'm new to the list. :)

--
Melissa Evans                               melissae at greyskies dot org

           No amount of planning will ever replace dumb luck.

On Mon, 11 Mar 2002, Vestal, Roy L. wrote:

> Works great! Here is the fix:
> 
> hosts.deny:
> all:all
> 
> hosts.allow:
> all: 192.168.0.1
> all: 192.168.0.2
> all: 192.168.
> 
> 
> Thanks again!
> 
> -----Original Message-----
> From: James Manning [mailto:trilug at sublogic.com]
> Sent: Monday, March 11, 2002 10:32 AM
> To: 'Trilug-Triangle Linux Users Group'
> Subject: [TriLUG] Re: Problems with hosts.deny hosts.allow
> 
> 
> [Vestal, Roy L.]
> > What I want to do is to set it up so that A and B can telnet, FTP, SSH,
> and
> > VNC to C.  If I remove "all:all" from hosts.deny, then they can. If I add
> > "all:all" then they cannot. I've added "192.168.0.1" and "192.168.0.2" to
> > machine C's hosts.allow, but I still cannot connect ("connection closed by
> > foreign host" error).
> 
> My guess would be "ALL: 192.168.0.1" and "ALL: 192.168.0.2" breaking
> out the service as desired.  Just a guess
>