https://bugzilla.novell.com/show_bug.cgi?id=878028 https://bugzilla.novell.com/show_bug.cgi?id=878028#c0 Summary: default config of fail2ban points to non existing log file Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: wagner-thomas@gmx.at QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (Windows NT 6.1; WOW64; Edition Campaign 21) Presto/2.12.388 Version/12.17 The default config of fail2ban /etc/fail2ban/jail.conf has loads of default entries which point to log files that are not used per default by openSUSE. E.g.
[ssh-iptables]
enabled = false filter = sshd action = iptables[name=SSH, port=ssh, protocol=tcp] sendmail-whois[name=SSH, dest=you@example.com, sender=fail2ban@example.com, sendername="Fail2Ban"] logpath = /var/log/sshd.log maxretry = 5
points to /var/log/sshd.log but per default, openSUSE logs ssh entries to /var/log/messages. Also the log-file /var/log/fail2ban remains empty. So nothing gets ever noticed by fail2ban. Reproducible: Always Steps to Reproduce: 1. default installation of openSUSE 13.1 2. sudo zypper in fail2ban 3. systemctl fail2ban start Actual Results: Fail2ban does not block anything. Expected Results: Fail2ban should at least work for elementary services like ssh out-of-the-box. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.