Bug#648021: fail2ban: Logfile in UTC, localtime UTC+1 - no entrioes found

2013-12-23 Thread Helmut Grohne
On Tue, Nov 08, 2011 at 01:01:23PM +0100, a...@old-forest.org wrote: On this (hopefully quite generic) system a log line looks: Nov 8 11:19:38 bar sshd[25427]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=fnord The time given is in UTC, localtime

Bug#648021: fail2ban: Logfile in UTC, localtime UTC+1 - no entrioes found

2011-11-09 Thread Arne Wichmann
begin quotation from Yaroslav Halchenko (in 2008125849.gz8...@onerussian.com): On Tue, 08 Nov 2011, a...@old-forest.org wrote: My workaround is 'fail2ban-client set ssh findtime 4600', which is a bit ugly. A nicer approach would be to make a time offset settable. hm... i.e.

Bug#648021: fail2ban: Logfile in UTC, localtime UTC+1 - no entrioes found

2011-11-08 Thread aw
Package: fail2ban Version: 0.8.4-3 Severity: normal Hi. On this (hopefully quite generic) system a log line looks: Nov 8 11:19:38 bar sshd[25427]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=fnord The time given is in UTC, localtime is UTC+1.

Bug#648021: fail2ban: Logfile in UTC, localtime UTC+1 - no entrioes found

2011-11-08 Thread Yaroslav Halchenko
On Tue, 08 Nov 2011, a...@old-forest.org wrote: My workaround is 'fail2ban-client set ssh findtime 4600', which is a bit ugly. A nicer approach would be to make a time offset settable. hm... i.e. custom time offset per each jail? --