Hi, 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[7655]: Got exit signal, flushing blocked > addresses and exiting... > Jun 16 01:00:00 blizzard sshguard[8080]: 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. Regards, Brix -- Henrik Brix Andersen <b...@freebsd.org>
PGP.sig
Description: This is a digitally signed message part
