FS#32162 - [sshguard]Could not resolve hostname in whitelist at startup

Attached to Project: Community Packages
Opened by Gabriel Machado (Geek2France) - Monday, 22 October 2012, 20:22 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Wednesday, 24 October 2012, 13:36 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Massimiliano Torromeo (mtorromeo)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Sshguard couldn't resolve hostname at startup. So the whitelist file works partially. Lines with ip addresses works but thus with hostnames doesn't work.

Additional info:
- package version : sshguard 1.5.6

/etc/sshguard_whitelist :
myhostname.dyndns.org

journalctl :
Oct 22 20:53:40 hostname sshguard[260]: Could not resolve hostname 'myhostname.dyndns.org': Name or service not known.
Oct 22 20:53:40 hostname sshguard[260]: whitelist: Unable to handle line 1 from whitelist file "/etc/sshguard_whitelist".


Steps to reproduce:
Configure sshguard to load a whitelist containing hostname(s).
Configure systemd to start sshguard at startup and reboot the server.
Launch journalctl command.

I think, sshguard systemd script miss a dependancy to launch the processes for dns name resolution.
This task depends upon

Closed by  Massimiliano Torromeo (mtorromeo)
Wednesday, 24 October 2012, 13:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  sshguard-1.5-7
Comment by Massimiliano Torromeo (mtorromeo) - Wednesday, 24 October 2012, 13:32 GMT
I am updating sshguard service to start after network. If this is not sufficient to satisfy your needs you should just override the service file with you own version.

Loading...