From: Tom H. <to...@wh...> - 2013-03-10 20:35:14
|
On 10/03/13 20:14, al...@ma... wrote: > Hi Fabian, > >> Why does this come up again? > > It comes up again because nothing was done by fail2ban to stop it - we > continue to get such false abuse complaints regularly, here is snippet of > "log evidence" from one of the most recent: > All of this has already been discussed, including responsibility of the the fail2ban developers, end-users, ISPs relaying complaints, and your company. I don't even know by heart what the final statements were, but I'm pretty much sure that this horse has been beaten to death a long time ago. So please stop it. fail2ban works really simple: - you can write *any* regex - apply that regex on *any* log file - execute *any* command based on that Sensible and useful defaults are added by the developers, and none of them do any harm to your business. That will never stop users from adding other configurations. Maybe your legal department could write a standard reply template for f2b generated complaints targeted at the both the end user and the relaying ISP, and use that to aid your volunteers. You're free to add pointers to all of your provided arguments and the f2b community agreeing (or not) with them, available in the mailing list archives. You're also free to contribute a short (5 lines?) text explaining your concerns on apache access blocking on the wiki [1], but you have to accept the simple fact that f2b cannot block users in any way from configuring the software to do something you don't like. [1] http://www.fail2ban.org/wiki/index.php/Apache Kind regards, Tom |