nextcloud: Remove fail2ban jail, brute force protection present

Nextcloud has a built-in brute force protection[1]. Combined with good password
policies, fail2ban is not required. Built-in protection is better than fail2ban
because, fail2ban makes the service unavailable which causes some confusion to a
genuine user.

Links:

1) https://docs.nextcloud.com/server/19/admin_manual/configuration_server/bruteforce_configuration.html

Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
This commit is contained in:
Sunil Mohan Adapa 2024-04-05 16:32:13 -07:00 committed by James Valleroy
parent 7ab7d949af
commit c371f77e3b
No known key found for this signature in database
GPG Key ID: 77C0C75E7B650808
3 changed files with 0 additions and 13 deletions

View File

@ -72,8 +72,6 @@ class NextcloudApp(app_module.App):
dropin_configs = DropinConfigs('dropin-configs-nextcloud', [
'/etc/apache2/conf-available/nextcloud-freedombox.conf',
'/etc/fail2ban/jail.d/nextcloud-freedombox.conf',
'/etc/fail2ban/filter.d/nextcloud-freedombox.conf',
'/etc/redis/conf.d/freedombox.conf',
])
self.add(dropin_configs)

View File

@ -1,7 +0,0 @@
[INCLUDES]
before = common.conf
[Definition]
_daemon = apache-access
prefregex = %(__prefix_line)s
failregex = \S+ <HOST>(?::\d+)? - \S+ \[[^\]]*\] "GET /nextcloud/login\?direct=1&user=\S+ HTTP/\S+" 200

View File

@ -1,4 +0,0 @@
[nextcloud-freedombox]
enabled = true
filter = nextcloud-freedombox
journalmatch = SYSLOG_IDENTIFIER=apache-access