[ale] Can't Telnet Into Debian 2.2

[Bao Ha]

Can you explicitly specify the allowd hosts in /etd/hosts.allow
file?

It is a compilation switch.  Debian "strives" to be as secure
out of the box as possible.  I don't neccessarily agree, but
it has saved my butt many times with attacks, while RH fails
miserably.

Bao

> -----Original Message-----
> From: owner-ale at ale.org [mailto:owner-ale at ale.org]On Behalf Of Jeff
> Hubbs
> Sent: Saturday, March 17, 2001 7:39 PM
> To: David Corbin
> Cc: ale at ale.org
> Subject: Re: [ale] Can't Telnet Into Debian 2.2
> 
> 
> 
> > You have, of course, checked the debian system log files, right?  My
> > guess is you'll find that tcpd is dropping you.  This 
> happens for oen of
> > two reasons (in my experience): /etc/hosts.allow & 
> /etc/hosts.deny are
> > not set to allow your host access, or more commonly, when the Debian
> > system does a reverse DNS lookup on the incoming address, it fails
> > outright or fails to match the forward looking DNS. i.e., 
> if you're IP
> > address is w.x.y.z, not only does "nslookup w.x.y.z have to yield
> > "foo.bar.com", but "nslookup foo.bar.com" has to yield "w.x.y.z".
> 
> Well, I might have a little trouble with that, since 1) I don't appear
> to have nslookup and 2) I have no internal DNS present - in fact, I'm
> setting this machine up to BE the DNS!  It has a host table, just like
> the Mandrake machine that can be telnetted to without problem.  I've
> been having a problem in that if I need, for instance, 
> nslookup, I have
> no idea what to "apt-get install" to get it (thankfully emacs did not
> present this problem).
> 
> If I understand you, then, telnetting to the Debian box just 
> isn't going
> to work until I get it running as a DNS.  Why is it that 
> Mandrake deals
> while Debian does not?
> 
> - Jeff
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" 
> in message body.
> 

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.