Marshall Dudley wrote: > I previously asked about the message I got the other day: > > WARNING: The following hosts appear in /etc/hosts.allow but should be > allowed based on your /usr/share/denyhosts/data/allowed-hosts file: > > 69.130.129.103 (h69-130-129-103.69-130.unk.tds.net) > > The only reply I got was talking about a hosts.deny file. This is a > freebsd system and there is no hosts.deny file, both the denys and > allows are put into the hosts.allow file with the following format: > > ALL : 111.222.123.234 : allow > > for allow and > > ALL: 111.222.123.234 : deny > > for deny. > > I have my ip in the hosts.allow to always allow me, and I also have it > in the trusted ips for denyhosts. It sent me the above email. I am not > certain if this is a problem, or if I should just ignore it.
>From the man hosts_options: "The allow and deny keywords make it possible to keep all access control rules within a single file, for example in the hosts.allow file." That's what you are using and it's valid. You can also use a /etc/hosts.deny file at the same time. The response you received to your first message was that DenyHosts looks by default to the hosts.deny file and if it finds duplicates with the allowed-hosts it points them out. So the message unless it point out a contradiction is harmless. You can also get rid of the message by configuring DenyHosts to use /etc/hosts.deny keeping your /etc/hosts.allow (precedence between those two is hosts.allow wins over hosts.deny). -- René Berber Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Denyhosts-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/denyhosts-user
