Hi Erik, an interesting coincidence -- only yesterday there was similar report on f2b mailing list from a RHEL user:
http://sourceforge.net/mailarchive/forum.php?thread_name=20120124231706.GF16995%40onerussian.com&forum_name=fail2ban-users and I have tried to replicate but failed so far... and I did use syslog-ng as well... just now mentioned that I was using 0.8.6-1 not 0.8.6-2 but I don't think those changes were relevant (although who knows...) will need to dig in some time. thanks for the report On Wed, 25 Jan 2012, Erik Braun wrote: > Package: fail2ban > Version: 0.8.6-2 > Severity: minor > Dear Maintainer, > When using the logging target SYSLOG, the entries seem to be > prepended by a UTF-8 BOM. less says: > Jan 25 02:13:08 ppc624 <U+FEFF>fail2ban.actions: WARNING [ssh] Ban > 62.217.123.133 > Jan 25 02:23:08 ppc624 <U+FEFF>fail2ban.actions: WARNING [ssh] Unban > 62.217.123.133 > hexdump -C shows prior "fail2ban.actions": 'ef bb bf' > (maybe I had not noticed this, if my syslog-ng configuration were > not confused by it) > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (500, 'testing'), (90, 'unstable') > Architecture: amd64 (x86_64) > Kernel: Linux 2.6.38.2.linuxpool (SMP w/4 CPU cores; PREEMPT) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Versions of packages fail2ban depends on: > ii lsb-base 3.2-28 > ii python 2.7.2-9 > ii python-central 0.6.17 > Versions of packages fail2ban recommends: > ii iptables 1.4.12.2-1 > ii python-gamin <none> > ii whois 5.0.14 > Versions of packages fail2ban suggests: > ii bsd-mailx [mailx] 8.1.2-0.20111106cvs-1 > ii mailx 1:20081101-2 > -- Configuration Files: > /etc/fail2ban/fail2ban.conf changed [not included] > -- no debconf information -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
