Skip to content
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

Fail2ban - miab-munin.conf filter not cathing HTTP/2.0 #2358

Open
solomon-s-b opened this issue Jan 29, 2024 · 0 comments
Open

Fail2ban - miab-munin.conf filter not cathing HTTP/2.0 #2358

solomon-s-b opened this issue Jan 29, 2024 · 0 comments

Comments

@solomon-s-b
Copy link
Contributor

It appears that the filter.d/miab-munin.conf doesn't catch all failed login attempts to https://box.domain.tld/admin/munin because it only looks for HTTP/1.1 which leaves out HTTP/2.0.

I updated the filter as follow, so it will catch both 1.1 and 2.0 (the same way it is used in: filter.d/nginx-http-auth.conf) and it works perfectly:

failregex=<HOST> - .*GET /admin/munin/.* HTTP/\d+\.\d+" 401.*

I'll open a PR just in case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant