There is a new version of this port and needs to be updated, as the previous version was a little bit confusing in regards to service codes which seems to be fixed in this version. How-To-Repeat: http://www.sshguard.net/
Responsible Changed From-To: freebsd-ports-bugs->danger Submitter has GNATS access (via the GNATS Auto Assign Tool)
Maintainer of security/sshguard, Please note that PR ports/142469 has just been submitted. If it contains a patch for an upgrade, an enhancement or a bug fix you agree on, reply to this email stating that you approve the patch and a committer will take care of it. The full text of the PR can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/142469 -- Edwin Groothuis via the GNATS Auto Assign Tool edwin@FreeBSD.org
State Changed From-To: open->feedback Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
We were discussing with itetcu@ (who also submitted the sheer version = bump a while ago) that the next update to security/sshguard-* should be addressing http://www.mail-archive.com/freebsd-ports@freebsd.org/msg17930.html as well. However, the 1.5 version recently introduced includes the "log sucking" = feature. I favor the idea of offering that and removing the port's logic for updating syslog.conf = at all. Take this, and take this is the 4th request I receive to have sshguard-1.4 in the ports, = let's commit this version update, ignore the syslog.conf report, and wait a few weeks for 1.5 to address = that at the root.=
State Changed From-To: feedback->closed - patch commited