From owner-freebsd-ports-bugs@FreeBSD.ORG  Fri May 29 07:51:48 2015
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 6199C82A
 for <freebsd-ports-bugs@FreeBSD.org>; Fri, 29 May 2015 07:51:48 +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 4A4741DAB
 for <freebsd-ports-bugs@FreeBSD.org>; Fri, 29 May 2015 07:51:48 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4T7pmrE094359
 for <freebsd-ports-bugs@FreeBSD.org>; Fri, 29 May 2015 07:51:48 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 200499] [PATCH] security/py-fail2ban: Prevent config files to
 be changed on updates.
Date: Fri, 29 May 2015 07:51:47 +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: patch
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: theis@gmx.at
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200499-13-kmNvg79jRB@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200499-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-200499-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.20
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 May 2015 07:51:48 -0000

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

--- Comment #1 from theis@gmx.at ---
No.

Most software in the ports follow the philosophy that users copy the
configuration files and edit them. But fail2ban is different: you don't edit
the original .conf-files but do you changes and your changes only in
corresponding .local-files. E.g., to enable ssh you would create a file
jail.local with the lines
 [sshd]
 enabled = true
(plus other specifics) in it.

See the header of fail2ban.conf and jail.conf files.
This way you'll benefit from enhancements and fixes coming from upstream
without having to merge your files after every update or risk losing the
changes.

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