Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#5305 - denyhosts not using cfg file

Attached to Project: Arch Linux
Opened by Jon Wilson (DesertFox) - Monday, 28 August 2006, 16:27 GMT
Last edited by Dale Blount (dale) - Monday, 28 August 2006, 17:27 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Simo Leone (neotuli)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

It looks like the package denyhosts in extra is not using the /etc/denyhosts/denyhosts.cfg file. Denyhosts is a daemon, and all that needs to be done is add

--config=/etc/denyhosts/denyhosts.cfg to the /etc/rc.d/denyhosts start command to have it use the config file. would be useful if the build was updated.

It looks like some of the configuration is read, like the admin email address, but other important things, like how long to block an ip for, how many failed attempts in each category, etc are not correctly read unless the --config option is passed to the daemon.

Thanks
This task depends upon

Closed by  Simo Leone (neotuli)
Sunday, 24 September 2006, 18:35 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Seems this is an upstream issue. Don't be afraid to file another bug report here if it turns out to be an Arch-specific thing.
Comment by Robert Howard (iBertus) - Monday, 28 August 2006, 19:19 GMT
Thanks for adding this bug report, DesertFox. It should get handled here faster than in the pacman-dev list.
Comment by Jon Wilson (DesertFox) - Wednesday, 30 August 2006, 19:01 GMT
On further testing, it looks like the config file is loaded properly right now, but it is the delay on polling the auth.log which is causing the problems - ie - invalid logins are supposed to be locked with only 1 failed attempt, but usually it takes 3 or 4 - most likely due to someone trying faster than denyhosts checks the auth.log file. I guess that means this can either be closed, or maybe a new way of polling the file come up - perhaps inotify (which is in the defacto 2.6 kernel arch uses - CONFIG_INOTIFY)- which basically creats an interrupt on a file - whenever it changes an interrupt type event is generated - this would be less cpu intensive and would work better - should this be submitted to the denyhosts developers?

Thanks.
Comment by Dale Blount (dale) - Wednesday, 30 August 2006, 19:12 GMT
Yes, please report this upstream via sourceforge or the mailing list to see if they have ideas on why it takes so long.

Loading...