ports/163126: security/sshguard changed from syslog.conf to daemon boot script

Mij mij at bitchx.it
Mon Dec 19 17:30:11 UTC 2011


The following reply was made to PR ports/163126; it has been noted by GNATS.

From: Mij <mij at bitchx.it>
To: bug-followup at FreeBSD.org,
 freebsd at akruijff.dds.nl
Cc:  
Subject: Re: ports/163126: security/sshguard changed from syslog.conf to daemon boot script
Date: Mon, 19 Dec 2011 18:12:44 +0100

 I can see a few of reasons why people prefer boot scripts to syslog:
 
 * when run by syslog, every log rotation restarts sshguard, and so blocked
 addresses are reset.
 * it's simpler to maintain: if you want to stop/restart sshguard, syslog.conf
 is not where you'd look out of intuition.
 * it's more flexible. Many use sshguard to protect additional services that
 do not log through syslog.
 
 As to automatic upgrades, I wouldn't feel "stuck" with syslog or complex
 backward-compatibility knobs. A note in /usr/ports/UPDATING should do.
 
 I'll review this patch next weeks.



More information about the freebsd-ports-bugs mailing list