From owner-freebsd-ports@FreeBSD.ORG Wed Jun 15 17:17:36 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B606E10656D5 for ; Wed, 15 Jun 2011 17:17:36 +0000 (UTC) (envelope-from mail@ozzmosis.com) Received: from outbound.icp-qv1-irony-out2.iinet.net.au (outbound.icp-qv1-irony-out2.iinet.net.au [203.59.1.107]) by mx1.freebsd.org (Postfix) with ESMTP id 34A7B8FC19 for ; Wed, 15 Jun 2011 17:17:35 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtURAFXi+E18qEEv/2dsb2JhbABSmAMNjkV3yFqGJgSWGyuLCg X-IronPort-AV: E=Sophos;i="4.65,370,1304265600"; d="scan'208";a="754970536" Received: from unknown (HELO smtp.phoenix) ([124.168.65.47]) by outbound.icp-qv1-irony-out2.iinet.net.au with ESMTP; 16 Jun 2011 00:49:49 +0800 Received: by smtp.phoenix (Postfix, from userid 1001) id C54D5171F3; Thu, 16 Jun 2011 02:49:48 +1000 (EST) Date: Thu, 16 Jun 2011 02:49:48 +1000 From: andrew clarke To: freebsd-ports@freebsd.org Message-ID: <20110615164948.GA8660@ozzmosis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: mij@bitchx.it Subject: Upgrading sshguard X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2011 17:17:36 -0000 Hi, 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". 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) Regards Andrew