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

RFE: LOGGING for fail2ban #150

Open
fadamo opened this issue Aug 23, 2024 · 0 comments
Open

RFE: LOGGING for fail2ban #150

fadamo opened this issue Aug 23, 2024 · 0 comments

Comments

@fadamo
Copy link

fadamo commented Aug 23, 2024

I'm on RHEL 9.x, after every VAPT on our server I got this situation:

# systemctl --failed
  UNIT                                                    LOAD   ACTIVE SUB    DESCRIPTION
● [email protected]:1234-1.2.3.4:42434.service loaded failed failed Tang Server (1.2.3.4:42434)
● [email protected]:1234-1.2.3.4:42452.service loaded failed failed Tang Server (1.2.3.4:42452)
● [email protected]:1234-1.2.3.4:42454.service loaded failed failed Tang Server (1.2.3.4:42454)
● [email protected]:1234-1.2.3.4:42456.service loaded failed failed Tang Server (1.2.3.4:42456)
● [email protected]:1234-1.2.3.4:42458.service loaded failed failed Tang Server (1.2.3.4:42458)
● [email protected]:1234-1.2.3.4:42460.service loaded failed failed Tang Server (1.2.3.4:42460)
.....
.....

I'm trying to configure fail2ban, but I found it would be useful if you added the offending IP to the message:

HTTP Parsing Error: invalid HTTP method

and similar.
Right now I'm using this filter

failregex = .*tangd@.*-.*:1234-<HOST>:.*.service: Main process exited, code=exited, status=1/FAILURE
            tangd\[.*\]: <HOST> GET .* => 404 \(../src/http.c:.*\)

but it's not enough.

Thanks

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