Well, now I know why ALL: ALL in hosts.deny stopped things.
It turns out that hosts.allow does not allow "ALL: my.ip.address" but is
happy with "ALL: 203.x.y.z" or even "ALL: 203.x.y." There is a note about
this regarding the portmapper but I had not realised that the portmapper
is involved.
T
On Mon, Aug 07, 2000 at 09:51:50AM -0400, Noah L. Meyerhans wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> These are by no means irrelevant to sshd, even if it is not run from
> inetd. Read the man page for sshd, in which you'll see that it can be
> build with direct support for tcp_wrappers. I
-BEGIN PGP SIGNED MESSAGE-
These are by no means irrelevant to sshd, even if it is not run from
inetd. Read the man page for sshd, in which you'll see that it can be
build with direct support for tcp_wrappers. If it is (I don't know what
the configure options in the Debian build are, but
On Mon, Aug 07, 2000 at 09:48:13PM +0800, Lindsay Allen wrote:
>
> Hello world,
>
> I have a hosts_access problem.
>
> hosts.deny has the line
> ALL:ALL
>
> This stops me logging in with ssh. The problem is that if I put a line in
> hosts.allow like
> sshd: my.ip.address
> the rule does not
Hello world,
I have a hosts_access problem.
hosts.deny has the line
ALL:ALL
This stops me logging in with ssh. The problem is that if I put a line in
hosts.allow like
sshd: my.ip.address
the rule does not match because sshd does not feature in inetd.conf.
What have I missed?
Lindsay
--
5 matches
Mail list logo
