GitHub puppet-fail2ban
This module installs, configures and manages the Fail2ban service.

Repo Checks ( 11 of 17 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Supports Only Current Debian
No translation
failed
Supports Latest Debian
No translation
failed
Supports Only Current Ubuntu
No translation
failed
Supports Latest Ubuntu
No translation
passed
Supports Only Current Centos
No translation
failed
Supports Latest Centos
No translation
passed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
passed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
failed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
failed

Open Pull Requests

initial support for opensuse

Pull Request (PR) description

Adding support for OpenSuSE

This Pull Request (PR) fixes the following issues

Does not work on OpenSuSE

Open PR in GitHub
Fix apache-badbots on RedHat

These lines were probably commented out by mistake in refactoring (d9d2d03d396fb1d24ff7602d253c9748c99b9cdc).

Btw. there are no acceptance tests for RedHat, it might be safer to use Centos templates (if there are no substantial differences).

Open PR in GitHub
Allow changing the ports of the fail2banned services
merge-conflicts
needs-work

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

This request allows changing the default port for any service watched by fail2ban. Check Readme.md for the usage of the "ports" parameter.

Most changes made in this request are just ternary operators on templates and the addition of the "ports" parameter hash to init.pp

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

Adds feature: Allow modification of default ports for each service

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
Add AlmaLinux & Rocky config, identical to CentOS. This fixes the module on A…

Pull Request (PR) description

Copy Centos8 Jail Config template to AlmaLinux/8 and Rocky/8 resolves missing template on AlmaLinux 8.x and Rocky 8.x

This Pull Request (PR) fixes the following issues

No Issues opened, just submitting a patch :)

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Could not find template 'fail2ban/AlmaLinux/8/etc/fail2ban/jail.conf.epp' (file: /etc/puppetlabs/code/environments/R20210608/modules/fail2ban/manifests/init.pp, line: 51, column: 26) on node

Open PR in GitHub
This commit addresses some basic levels of control not possible befor…

…e per https://github.com/voxpupuli/puppet-fail2ban/issues/157

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
[WIP] Support overriding configuration for default jails

The PR addresses the same issue as #48 but with a bit more generic approach.

Using 2 level Hash might be possible to override basically any attribute in the template.

yaml
fail2ban::jails:
- ssh
- ssh-ddos
fail2ban::jails_config:
ssh:
port: 'ssh,2200'
ssh-ddos:
port: 'ssh,2200'

Using lookup() in templates might not be the best approach, but I can't think of better alternative. Passing explicitly each variable explicitly to the template would generate loads of code. Another option is to write a custom function for checking key existence in the configuration hash (but it doesn't add much to code readability).

Let me know if you're ok with this, so that I'm able to proceed with modifying rest of jails.

Open PR in GitHub
WIP: Add support for package install options
needs-tests
enhancement

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Add support for package install options.
See puppet package resource for more info:
https://puppet.com/docs/puppet/7/types/package.html#package-attribute-install_options

Open PR in GitHub