move the fail2ban rules under the dsa-f2b chain

[mirror/dsa-puppet.git] / modules / fail2ban / manifests / init.pp

diff --git a/modules/fail2ban/manifests/init.pp b/modules/fail2ban/manifests/init.pp
index 3051b99..8d64034 100644 (file)
--- a/modules/fail2ban/manifests/init.pp
+++ b/modules/fail2ban/manifests/init.pp
@@ -7,6 +7,11 @@ class fail2ban {
                ensure  => running,
        }
 
+       file { '/etc/fail2ban/jail.d/dsa-00-default.conf':
+               source => 'puppet:///modules/fail2ban/jail/dsa-00-default.conf',
+               notify  => Service['fail2ban'],
+       }
+
        @ferm::conf { 'f2b':
                content  => @(EOF),
                                @hook post  "type fail2ban-client > /dev/null && (fail2ban-client ping > /dev/null && fail2ban-client reload > /dev/null ) || true";
@@ -14,4 +19,20 @@ class fail2ban {
                                | EOF
        }
 
+       @ferm::rule { 'dsa-f2b-setup':
+               prio        => '005',
+               description => 'f2b master rule',
+               chain       => 'INPUT',
+               domain      => '(ip ip6)',
+               rule        => 'saddr 0/0 @subchain "dsa-f2b" {}'
+       }
+
+       # XXX Maybe this will be automatically done in buster, it is certainly needed in stretch. So maybe:  versioncmp($::lsbmajdistrelease, '9') <= 0
+       concat::fragment { 'dsa-puppet-stuff--fail2ban-cleanup':
+               target => '/etc/cron.d/dsa-puppet-stuff',
+               content  => @(EOF)
+                       17 * * * * root python3 -c "import sys, logging; logging.basicConfig(stream=sys.stdout, level=logging.INFO); from fail2ban.server.database import Fail2BanDb; db = Fail2BanDb('/var/lib/fail2ban/fail2ban.sqlite3'); db.purge(); db._db.cursor().execute('VACUUM')"
+                       | EOF
+       }
+
 }