Date: Fri, 29 May 2015 07:51:47 +0000 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. 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200499-13-kmNvg79jRB>