From: "Paul Kölle" <pkoelle@gmail.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] iptables && fail2ban
Date: Tue, 15 Sep 2009 09:27:43 +0200 [thread overview]
Message-ID: <fa9631250909150027k61a05ce7ycb2e30ad8afaec24@mail.gmail.com> (raw)
In-Reply-To: <4AAE96C9.3090900@buanzo.com.ar>
On Mon, Sep 14, 2009 at 9:17 PM, Arturo 'Buanzo' Busleiman
<buanzo@buanzo.com.ar> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> paul kölle wrote:
>> Not really. IMO all these brute-force-polling-logwatcher are pretty bad
>> design. If proftpd uses pam you should search for pam_shield, it can
>> recognize failed logins and insert the appropriate rules into your
>> firewall.
>
> You've just stated a particular set of cases: applications that do auth and support pam.
>
> fail2ban is also used with fastcgi, lighttpd, apache, mod_security, nagios, etc, etc, etc.
>
> and polling is the fallback method....
>
> anyway, subjective opinon here, i'm one of fail2ban developers :P - don't take me seriously.
Sorry man, I didn't want to bash you work. Of course pam_shield is
limited to pam-enabled apps but in that cases it's better suited as it
can actually tell if there was a failed *login*. I hope we can agree
here ;)
cheers
Paul
>
> - --
> Arturo "Buanzo" Busleiman / Arturo Busleiman @ 4:900/107
> Independent Linux and Security Consultant - SANS - OISSG - OWASP
> http://www.buanzo.com.ar/pro/eng.html
> Mailing List Archives at http://archiver.mailfighter.net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEAREKAAYFAkqulskACgkQAlpOsGhXcE2vLACfYog8xe6K8o71kxu2WrdBZcLn
> qhcAniFwShclOrirUE+wQKQHEOxxTA5l
> =BCAP
> -----END PGP SIGNATURE-----
>
>
next prev parent reply other threads:[~2009-09-15 7:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 12:16 [gentoo-server] Iptables Changes Ajai Khattri
2008-09-22 12:28 ` Ryan Gibbons
2008-09-22 12:43 ` Ajai Khattri
2008-09-22 13:56 ` Kerin Millar
2008-09-22 15:21 ` Mark
2008-09-22 15:25 ` Andrew Gaffney
2008-09-22 17:53 ` Thilo Bangert
2008-09-23 12:21 ` Jozef [jonyii] Svec
2008-09-23 19:25 ` [gentoo-server] SPAM protection by requesting confirmation Alex Efros
2008-09-23 21:45 ` Ramon van Alteren
2008-09-24 0:13 ` Lindsay Haisley
2008-09-24 15:40 ` Matthias Bethke
2008-09-28 13:21 ` Alex Efros
2008-09-28 13:26 ` Alex Efros
2008-09-28 19:41 ` Homer Parker
2008-09-28 20:02 ` Alex Efros
2008-09-28 21:07 ` Homer Parker
2008-09-28 21:49 ` Alex Efros
2008-09-24 3:14 ` Homer Parker
2008-09-24 8:51 ` Oliver Schad
2008-09-24 15:58 ` Lindsay Haisley
2008-09-24 10:02 ` Thilo Bangert
2008-09-22 16:24 ` [gentoo-server] Iptables Changes Kerin Millar
2008-09-22 16:31 ` Marko Reiner
2008-09-22 16:43 ` Mark
2008-09-22 17:36 ` Roger Bumgarner
2008-09-24 23:05 ` Ajai Khattri
2009-08-02 9:17 ` [gentoo-server] iptables && fail2ban mrfroasty
2009-08-01 9:53 ` Kerin Millar
2009-08-02 11:24 ` mrfroasty
2009-08-01 18:06 ` Homer Parker
2009-08-03 21:42 ` mrfroasty
2009-08-08 14:40 ` Ajai Khattri
2009-08-08 20:20 ` mrfroasty
2009-08-08 23:07 ` paul kölle
2009-09-14 19:17 ` Arturo 'Buanzo' Busleiman
2009-09-15 7:27 ` Paul Kölle [this message]
2009-08-08 20:36 ` mrfroasty
2009-08-08 1:07 ` Steve Dommett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa9631250909150027k61a05ce7ycb2e30ad8afaec24@mail.gmail.com \
--to=pkoelle@gmail.com \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox