You are not logged in.
Pages: 1
My hosts.deny looks like
ALL: ALL: DENY
My hosts.allow I had to edit like this to get sshd "working".
sshd: ALL
But after installing Apache, well, it just worked, even though these hosts-files aren't supposed to allow it....unless they work in a very unlogical way
Just curious, thanks if anyone can explain
Offline
Hi Seb74,
I think that apache doesn't use tcp wrapper mechanism; so hosts.deny or hosts.allow don't work with it.
Offline
Hi Seb74,
I think that apache doesn't use tcp wrapper mechanism; so hosts.deny or hosts.allow don't work with it.
Didn't get much of what you said, but ok, there seems to be some explanation for it. Some (most?) services aren't stopped by hosts.deny.
Thanks
Offline
I have a related question that came up at work the other day...is there a way to limit httpd access to a specific IP address range if you can't use <code>hosts.allow</code> and <code>hosts.deny</code>?
Offline
If you run ldd on a binary and see libwrap.so in the output then it has tcpwrapper support.
elasticdog: http://httpd.apache.org/docs/2.2/howto/access.html
1000
Offline
But what does tcpwrapper mean?
I think you can enter access rights in httpd.conf, but usually everyone has on allow all, but you can set IP's there I think instead.
Offline
Ahh HA! Thanks byte!
Offline
Pages: 1