Pseudonomous
May 6th, 2009, 10:50 PM
Hello Everybody,
I'm somewhat new to the Debian/Ubuntu world, I've been using Arch Linux for about a year and half (and still am on my non-desktop machine), anyway, I'm trying to setup a secured remote access via ssh and I'm trying to deny hosts using tcp wrappers but it doesn't seem to be working.
Currently my hosts.allow file is empty and my hosts.deny file looks like:
ALL : ALL
this is based off of advice from:
http://ubuntuforums.org/showthread.php?t=937270&highlight=hosts.allow
I've also tried copying the hosts.allow file from my laptop (running arch linux):
ALL: ALL: DENY
On which I know the tcp wrappers work.
But either way I can still login from laptop, which should be denied. So I'm wondering why this isn't working; I have the same problem with a virtual machine running Debian. There are obvious ways to sidestep this problem, e.g. use a firewall instead of tcp-wrappers, but I'd still like to know why this doesn't work. Any help would be appreciated.
Thanks!
I'm somewhat new to the Debian/Ubuntu world, I've been using Arch Linux for about a year and half (and still am on my non-desktop machine), anyway, I'm trying to setup a secured remote access via ssh and I'm trying to deny hosts using tcp wrappers but it doesn't seem to be working.
Currently my hosts.allow file is empty and my hosts.deny file looks like:
ALL : ALL
this is based off of advice from:
http://ubuntuforums.org/showthread.php?t=937270&highlight=hosts.allow
I've also tried copying the hosts.allow file from my laptop (running arch linux):
ALL: ALL: DENY
On which I know the tcp wrappers work.
But either way I can still login from laptop, which should be denied. So I'm wondering why this isn't working; I have the same problem with a virtual machine running Debian. There are obvious ways to sidestep this problem, e.g. use a firewall instead of tcp-wrappers, but I'd still like to know why this doesn't work. Any help would be appreciated.
Thanks!