I can see it's getting parsed but it is completely ignored after that and it is causing our normal network operations grief because servers are being banned when they shouldn't be.
Possible user error. Awaiting response from reporter.
Most likely, the IPs in question are already in the OTHER WORK_DIR files--
if you stop DH, remove the IPs from the OTHER files and restart DH then
things should behave properly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
summary: HIGH-PRIORITY allowed-hosts being ignored causing grief --> allowed-hosts being ignored causing grief
status: open --> open-postponed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-11-10
Still not working properly.
My /var/lib/denyhosts/allowed-hosts:
127.0.0.0/8
10.8.0.0/16
192.168.0.0/22
My /etc/hosts.deny:
sshd:127.0.0.1
Definitely purged it before. I do realise that whitelisting is not the project's priority since you can use hosts.allow for that, but it's still annoying as hell.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=420501
Originator: NO
Possible user error. Awaiting response from reporter.
Most likely, the IPs in question are already in the OTHER WORK_DIR files--
if you stop DH, remove the IPs from the OTHER files and restart DH then
things should behave properly.
Still not working properly.
My /var/lib/denyhosts/allowed-hosts:
My /etc/hosts.deny:
Definitely purged it before. I do realise that whitelisting is not the project's priority since you can use hosts.allow for that, but it's still annoying as hell.