fail2ban vs. syslogd compression (to be solved soon)

2007-09-06 Thread Maxim Kammerer
Just to conclude the thread: I wrote to the author, Cyril Jaquier. This was his answer: snip I have received a patch from Stephen Gram for this. I will review this as soon as possible and will commit this to 0.8 branch. So it should be available in the next 0.8 release. /snip I have no clue what

Re: fail2ban vs. syslogd compression (to be solved soon)

2007-09-06 Thread Justin Piszcz
On Thu, 6 Sep 2007, Maxim Kammerer wrote: Just to conclude the thread: I wrote to the author, Cyril Jaquier. This was his answer: snip I have received a patch from Stephen Gram for this. I will review this as soon as possible and will commit this to 0.8 branch. So it should be available in

Re: fail2ban vs. syslogd compression (to be solved soon)

2007-09-06 Thread Stephen Gran
This one time, at band camp, Maxim Kammerer said: I have no clue what this patch looks like. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440037 -- - | ,''`.Stephen Gran | | : :'

Re: fail2ban vs. syslogd compression

2007-09-01 Thread Mark Brown
On Thu, Aug 30, 2007 at 11:42:03AM +0200, Maxim Kammerer wrote: 1) Clarify if it is really true that the message last message repeated \d+ times does not always refer to the last message, as suggested in one post. I thought that syslogd's raison d'etre was exactly to provide a unified

Re: fail2ban vs. syslogd compression

2007-08-31 Thread Dan Ritter
On Fri, Aug 31, 2007 at 12:34:13PM +0100, G.W. Haywood wrote: Most people on dynamic IPs don't have the same address for more than a day! Yes, you'll be an innocent victim of the spammers, but normally only if you try to send mail directly to our mailservers. In which case we don't want it,

Re: fail2ban vs. syslogd compression

2007-08-30 Thread Maxim Kammerer
Ok, thanx to everybody for the advice. I am no step closer to a solution however. I see different routes: 1) Clarify if it is really true that the message last message repeated \d+ times does not always refer to the last message, as suggested in one post. I thought that syslogd's raison d'etre

Re: fail2ban vs. syslogd compression

2007-08-30 Thread Jack T Mudge III
On Wednesday 29 August 2007 03:56, G.W. Haywood wrote: Most offenders are blocked permanently, at the last count we're blocking about 27,750 ranges.  Our scripts could handle the 'repeat' messages if they needed to, but they don't.  The script kiddies don't get five tries, we block them after

Re: fail2ban vs. syslogd compression

2007-08-29 Thread G.W. Haywood
Hi there, On Tue, 28 Aug 2007, Maxim Kammerer wrote: I believe this belongs to the security-mailing list. Agreed. :) ... pop3-cracking attempts ... stupid ... There's a lot of it about. They'll try ftp, irc, ssh and http as well. In fact they'll try anything that offers them a connection.

fail2ban vs. syslogd compression

2007-08-28 Thread Maxim Kammerer
Hello everybody, I believe this belongs to the security-mailing list. I recently took a server online and it was immediately hit by pop3-cracking attempts. Well, they were quite stupid, since they were attempting once for each name taken from a 'frequent names list', so I guess somebody was

Re: fail2ban vs. syslogd compression

2007-08-28 Thread dann frazier
On Tue, Aug 28, 2007 at 12:43:10PM +0200, Maxim Kammerer wrote: Hello everybody, I believe this belongs to the security-mailing list. I recently took a server online and it was immediately hit by pop3-cracking attempts. Well, they were quite stupid, since they were attempting once for each

Re: fail2ban vs. syslogd compression

2007-08-28 Thread Bernd Eckenfels
In article [EMAIL PROTECTED] you wrote: Wouldn't a better option be to teach fail2ban how to parse the last message repeated.. messages? Maxim or Dann: When you find out how to do that, please post it to the list for archiving / information-sharing purposes. I can tell you the obvious: