You’ve probably gone from v8 or lower. There are major changes in the way
jails are configured in v0.9 and up.
Configurations are now done using .local files and there’s also been lots
of syntax changes which if you are using an old fail2ban.conf will cause it
to not work.
Have a look through the d
Hi,
I have been running f2b on a Debian Stable server for a long time.
Yesterday I upgraded the server to Debian Testing and with that came
fail2ban 0.9.6-1. For starters the service would not start, but I got
that fixed:
systemctl status fail2ban.service
● fail2ban.service - Fail2Ban Service
What are you actually trying to achieve ???
If you want a filter that can scan your logs looking for 403 and 444
errors, I wrote a custom filter below which works very well for me. It
picks up any excessive amounts of 403 or 444 errors generated by a client
and bans them for one day. Not sure if i
Sorry, full lines:
185.93.180.104 - - [18/Feb/2017:19:15:33 +] "POST /login.php
HTTP/1.1" 403 162 "-" "() { OpenVAS:; };
185.93.180.104 - - [18/Feb/2017:19:15:33 +] "POST /index.php
HTTP/1.1" 403 162 "-" "-" 0.000
Thanks
On 02/19/2017 07:02 AM, Dudi Goldenberg wrote:
>
> These lines do
