Hi, I have the following configuration on my hosts.deny and hosts.allow:

/etc/hosts.deny
ALL : ALL

/etc/hosts.allow
ALL : 127.0.0.1

What I want is to allow a specific user to connect to ssh server from anywhere, something like:

sshd: <usrname>@ALL

but this isn't working, can someone tell me how to do this?

Thanks,
Bruno

tcpwrappers can not know what a user name is, that's something handled by the daemon it is wrapping, and at TCP level there is no such concept as a user name. tcpwrappers does support RFC931 http://www.faqs.org/rfcs/rfc931.html but that itself relies on finger services on the client side to tell tcpwrappers outside of the appliction who the user is. it's really no use unless you control both the client and the server.

/etc/hosts.allow
ALL : 127.0.0.1
You'll have to add a line with the first argument set to the argv[0] of the binary ("sshd" in this case) and allow the subnets the user is allowed from. With "/24" subnet type notation just chop of the last octet. Example with subnet "11.22.33.44":
sshd: 127.0.0.1, 11.22.33.,
This will allow anyone with access through ssh to connect. "man 5 hosts_access" for more info.
Also make sure your firewall policy reflects this policy.

Now set in sshd_config the AllowUsers directive to "user@host" and make sure you include all the users that are allowed in. (You can also use the PAM listfile module instead, but that only works with usernames, no hosts, unless you also set access.conf.) If you want to further restrict subnets this user is allowed in from you can add "from="127.0.0.1,11.22.33.44"" to the users ~/.ssh/authorized_keys key entry, unless the user needs to change (add authed keys to) the file.

But I want to access from several different places, not only a subnet, and my firewall policy is according.
Can I take this approach:

sshd : ALL

and allow only my username using sshd_config?
Also, can I change ALL : 127.0.0.1 to ALL : LOCALHOST? Is it the same?

Thanks for all.

absolutely, yes. it's not until you get to ssh itself that the idea of a username comes into existance, but once it has you can certainly leverage a combination of tcpwrappers and sshd_config to control things quite tightly.