Henrik Brix Andersen
brix at FreeBSD.org
Wed Jun 15 18:08:02 UTC 2011
On Jun 15, 2011, at 18:49, andrew clarke wrote:
> A recent FreeBSD ports change upgrades sshguard to 1.5. I'm not sure
> about other variants, but with sshguard-ipfw at least, from what I can
> tell, installing the port erroneously comments-out the following
> existing line from /etc/syslog.conf:
> auth.info;authpriv.info | exec /usr/local/sbin/sshguard
> To get sshguard-ipfw to work again you need to uncomment the above
> line and restart syslogd, eg. "sudo service syslogd restart".
Yes, this happens with sshguard-pf and plain old sshguard as well.
> Incidentally version 1.5 is somewhat more "noisy" than the previous
> version, sending this to /var/log/messages once every few hours:
> Jun 16 01:00:00 blizzard sshguard: Got exit signal, flushing blocked addresses and exiting...
> Jun 16 01:00:00 blizzard sshguard: Started successfully [(a,p,s)=(40, 420, 1200)], now ready to scan.
> (obviously a separate issue to the syslog.conf problem above)
That's not new.
As I noted on the in a reply to the commit mail, sshguard 1.5 also breaks the -b flag.
Henrik Brix Andersen <brix at FreeBSD.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 194 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20110615/94a7c1cf/PGP.pgp
More information about the freebsd-ports