Date: Wed, 30 Sep 2015 21:29:43 +0930 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: "Michael B. Eichorn" <ike@michaeleichorn.com>, Alexandre <axelbsd@ymail.com>, FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: SSHguard & IPFW Message-ID: <560BCEAF.20900@ShaneWare.Biz> In-Reply-To: <1443531575.1236.13.camel@michaeleichorn.com> References: <DUB118-W2564316B09E855F03F7D11B44E0@phx.gbl> <1443531575.1236.13.camel@michaeleichorn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29/09/2015 22:29, Michael B. Eichorn wrote:
> At a guess something happened to kick off sshguard without the rc script,
> but for most setups the rc script is the proper way to start sshguard.
>
> Is there any chance that you might have followed an old guide? In
> sshguard < 1.5 a valid configuration option was to use syslog to kickoff
> sshguard and not use sshguard enable, but this is now depreciated in
> favor of the new 'Log Sucker' introduced in v1.5.
No need for an old guide - using syslog instructions are given by the port.
cat /usr/ports/security/sshguard/files/pkg-message.in
##########################################################################
Sshguard installed successfully.
%%PKGMSG_FWBLOCK%%
If you would like to use sshguard via syslogd, add an entry to your
/etc/syslog.conf like the following:
auth.info;authpriv.info |exec %%PREFIX%%/sbin/sshguard
and use "/etc/rc.d/syslogd reload" to activate it. Note, you can add
additional arguments to the sshguard command if you so desire.
Alternatively, you can also start sshguard as a daemon by using the
rc.d script installed at %%PREFIX%%/etc/rc.d/sshguard .
See sshguard(8) and http://sshguard.sourceforge.net for additional info.
##########################################################################
--
FreeBSD - the place to B...Software Developing
Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?560BCEAF.20900>