Bug 200499 - [PATCH] security/py-fail2ban: Prevent config files to be changed on updates.
Summary: [PATCH] security/py-fail2ban: Prevent config files to be changed on updates.
Status: Closed Not A Bug
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2015-05-28 18:38 UTC by Danilo G. Baio
Modified: 2015-05-29 11:33 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (theis)

Attachments
py-fail2ban_patch_sample_files (1.02 KB, patch)
2015-05-28 18:38 UTC, Danilo G. Baio 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Danilo G. Baio freebsd_committer freebsd_triage 2015-05-28 18:38:03 UTC 
Created attachment 157231 [details]
py-fail2ban_patch_sample_files

Prevent config files to be changed on updates.
- Move fail2ban.conf and jail.conf to .sample extension.
- Add @sample on pkg-plist for both files.
Comment 1 theis 2015-05-29 07:51:47 UTC 
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.
Comment 2 Danilo G. Baio freebsd_committer freebsd_triage 2015-05-29 11:33:19 UTC 
Ok.
I got it.
Thanks for the feedback.