-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crowdsec: No ban occurs for Nextcloud #7018
Comments
* Add tainted nextcloud-logs.yaml parser NethServer/dev#7018
QA the goal is :
the target module ghcr.io/nethserver/crowdsec:1.0.10-dev.2
|
test case 1: VERIFIED In both cases,
|
released ghcr.io/nethserver/crowdsec:1.0.10 |
With Crowdsec we enable a jail to protect nextcloud against the brute force, however this jail is not working properly and this issue attempts to fix it
Steps to reproduce
Expected behavior
I expect that after 6 attempts you are banned during a period of time
Actual behavior
We are never ban for two reasons, the issue is in nextcloud-logs.yaml
nextcloud-app
and notnextcloud
Badly crowdsec does not support the overwrite of configuration file with a
.local
like crowdsecComponents
crowdsec:1.0.9
The text was updated successfully, but these errors were encountered: