From owner-freebsd-ports-bugs@freebsd.org  Fri Jul 21 16:23:03 2017
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD7D9DAB707
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Fri, 21 Jul 2017 16:23:03 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A64577582B
 for <freebsd-ports-bugs@FreeBSD.org>; Fri, 21 Jul 2017 16:23:03 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v6LGN3qn008645
 for <freebsd-ports-bugs@FreeBSD.org>; Fri, 21 Jul 2017 16:23:03 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 220906] security/sshguard
Date: Fri, 21 Jul 2017 16:23:03 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: chris@cretaforce.gr
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-220906-13-bl9k9tmxiv@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220906-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-220906-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 16:23:03 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220906

--- Comment #1 from chris@cretaforce.gr ---
This is the reply from the SSGuard developer Kevin Zheng:

"I took a look at the rc.d script in ports. SSHGuard usually looks at
sshguard.conf for a list of files to monitor, but lets you override it
via the command line using -l arguments.

Here, the rc.d script is *always* setting the '-l' arguments even if you
don't have SSHGUARD_WATCH_LOGS set in your rc.conf.

The right thing to do might be to change the rc.d script to avoid
setting '-l' arguments if the user left SSHGUARD_WATCH_LOGS empty. Or,
if easing the transition isn't important, axing it in favor of the
configuration file."

--=20
You are receiving this mail because:
You are the assignee for the bug.=