Package: fail2ban
Version: 0.8.13-1
Severity: important
Tags: patch
Dear Maintainer,
* What led up to the situation? Attempting to configure badips.com
reporting on banaction
* What exactly did you do (or not do) that was effective (or
ineffective)? Placed badips into default jail banaction
* What was the outcome of this action? 700 error in logs (included
below) since the category field remains blank
* What outcome did you expect instead? 200 in logs with proper category
-- Log Excerpt below (IPs redacted)
2015-10-02 15:22:32,330 fail2ban.actions.action[1692]: ERROR curl --fail
--user-agent "fail2ban v0.8.12" http://www.badips.com/add//RE.DAC.TE.D
returned 700
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages fail2ban depends on:
ii lsb-base 4.1+Debian13+nmu1
pn python:any <none>
Versions of packages fail2ban recommends:
ii iptables 1.4.21-2+b1
ii python-pyinotify 0.9.4-1
ii whois 5.2.7
Versions of packages fail2ban suggests:
ii bsd-mailx [mailx] 8.1.2-0.20141216cvs-2
pn python-gamin <none>
ii rsyslog [system-log-daemon] 8.4.2-1+deb8u1
-- Configuration Files:
/etc/fail2ban/action.d/blocklist_de.conf changed [not included]
/etc/fail2ban/jail.conf changed [not included]
-- no debconf information
Report will be sent to "Debian Bug Tracking System" <sub...@bugs.debian.org>
--
Justin Paglierani, Associate of (ISC)² working toward CISSP
(623) 999-6465
jpagl...@asu.edu
19c19
< category =
---
> category = <name>
