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
On Mon, Aug 07, 2000 at 04:05:19AM -0700, Eric G . Miller wrote:
> You're denying everyone and allowing no one. There's a good reason you
> can't connect ;). In /etc/hosts.allow, you could put:
no he is not, true there is nothing in hosts.allow, but all he has in
hosts.deny is ALL: PARANOID whic
-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
You're denying everyone and allowing no one. There's a good reason you
can't connect ;). In /etc/hosts.allow, you could put:
ALL: LOCAL
However, you shouldn't be running sshd from inetd -- it's too slow. If
you aren't running ssh from inetd, then you're problem is elsewhere.
Maybe check /etc/s
6 matches
Mail list logo
