All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
Standardise files with files in sous-chefs/repo-management
- Document missing service attributes
- CI: Switch to shared lint-unit workflow
- Standardise files with files in sous-chefs/repo-management
- Remove delivery folder
- Standardise files with files in sous-chefs/repo-management
- Chef 17 updates: enable
unified_mode
on all resources - Bump required Chef Infra Client to >= 15.3
- Add
bantime
property tofail2ban_jail
resource - Remove unsupported platforms
- Remove logic for fail2ban < 0.9
- Standardise files with files in sous-chefs/repo-management
- Fix jail template to not set
port
orlogpath
if not defined in the resource
- improves resource documentation in README
- fixes jail resource to support priority property in delete action
- Remove deprecated platform in spec tests
- fixed wrong property in
fail2ban_jail
andfail2ban_filter
resources - added documentation for above changes
- Migrated build system to github actions for testing
- Simplify platform check logic
- Fix several parts of the recipe that were not compatible with Amazon Linux
- Update all templates to use the same managed by chef warning
- Adds Slack notifications as a notifier
- Fixup testing
- Require Chef 13 or later
- Add support for Amazon Linux on Chef 13+
- Add support for Ubuntu 18.04
- Add new fail2ban_jail and fain2ban_filter resources that allow you to define individual filters and jails within your own recipes instead of using the monolithic attribute config. With the introduction of these resources the existing attribute driven workflow has been deprecated and will eventually be removed. Thank you OpenStreetMap for these great new resources.
- Update specs to the latest platform versions
- Testing updates
- Delete jail.d/00-firewalld.conf on CentOS like we delete jail.d/defaults-debian.conf on Ubuntu)
- Move templates out of the default directory
- Update the minimum supported Chef release to 12.9 since we're using the Ohai package plugin now. We highly recommend you run at least the very latest Chef 12 reelase which includes additional packabe plugin fixes.
- Add new logic to detect the fail2ban version and apply appropriate config for 0.8 vs > 0.8. This makes sure we're using the current on newer systems while still supporting Ubuntu 14.04
- Remove defunct syslog config statements from very old fail2ban releases
- Update apache2 license string
NOTE The next version of this cookbook will be a rewrite to use custom resources and eliminate attributes. This should be backwards compatible to previous versions of the cookbook, but there are some changes that might break current assumptions so doing a major bump.
- [#33] Fix ubuntu platforms
- Add ubuntu platform guards to default recipe
- Update README to be more clear with regards to rsyslog
- Remove defaults-debian.conf on ubuntu platforms, that assumes ssh enabled on nodes.
- Modify metadata dependency to Chef 12.5+
- Modify chef spec to remove service start, enable on resources as on debian platforms the service is started by install of package
- Make test kitchen show deprecation errors
- Remove EOL debian and ubuntu logic from default recipe
- Add support for jail ignorecommand
- Testing updates
- Require Chef 12.1+
- Add opensuse and opensuseleap to the metadata
- Added fixture cookbook
- Cleanup of kitchen configurations
- [#38] Default config values to avoid warning from pbanderas
- [#37] Add support for 'sendername' setting on config from Restless-ET
- [#35] Add support for configuring service backend from ares
- many updates to testing
- [#25] Allow jail actions of either format from rchekaluk
- Add OpenSUSE platform
- Updated Berksfile to 3.0 format
- Added "generated by chef" comment headers to all templates
- Added missing bantime service attribute to the readme
- Resolved all rubocop warnings
- Added yum-epel to the readme as a dependency
- Removed the dependency on the yum cookbook. This cookbook only requires yum-epel, which handles the yum dependency
- Added a chefignore file to prevent unnecessary files from being uploaded to the chef-server
- Changed fail2ban package to install only vs. upgrading. Administrators should be able to choose when packages are upgraded
- Change file mode definitions to be strings to preserve the leading zeros
- Added testing / cookbook version badges to the readme
- Added source_url and issues_url metadata for Chef 12
- Add basic cookbook convergence chefspec tests
- Updated the testing and contributing docs to more recent versions
- Bumped all development and testing gems to the latest versions
- Expanded Travis testing to ruby 2/2.1/2.2
- Changed Opscode to Chef Software in all locations
- [#24] Add default value for pidfile
- COOK-3899 - Allow action override in service block
Updating for cookbook yum ~> 3.0 Fixing style or rubocop Updating test bits
fixing metadata version error. locking to 3.0
Locking yum dependency to '< 3'
[COOK-2530] Allow customisation of jail.local
- COOK-3383 - Add clarifying caveat about rsyslog in README
- COOK-3249 - Fix default
jail.conf
on CentOS
- COOK-2748 - Handle
/etc.init.d/fail2ban status
for older versions
- [COOK-2588]: Fail2ban needs to store the socket in the correct location
- [COOK-2592]: fail2ban: Update jail file template to match current config file
- [COOK-2292] - Add fail2ban support for RHEL using EPEL
- [COOK-2426] - Fail2ban cookbook needs syslog tunables in config file
- Development repository only: test kitchen 1.0.alpha support
- [COOK-2291] - Add additional tunables to the fail2ban cookbook
- [COOK-2217] - Users should be able to configure the email address fail2ban uses to send messages
- Current public release.