All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Eric Marchionni <mailing-lists@gmx.ch>
Cc: Cedric Blancher <blancher@cartel-securite.fr>,
	netfilter@lists.netfilter.org
Subject: Re: deny cgi scanner
Date: Tue, 1 Apr 2003 15:06:52 -0500	[thread overview]
Message-ID: <20030401200652.GY18434@ns.snowman.net> (raw)
In-Reply-To: <3E89EBE5.5090804@gmx.ch>

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

* Eric Marchionni (mailing-lists@gmx.ch) wrote:
> as far as i understand this will result in a slowdowned scan.
> if somehow possible i'd like to abort the scan at all. like
> denying any connection from the attackers ip for about 1 minute 
> or so...
> (i know it's dangerous if someone begins spoofing google-ip or
> my dns-server-ip with a cronjob, but this would only affect the
> web-server...)
> 
> else i'll use iplimit ;-D

Use iplimit with ipt_recent and you can achieve exactly that.  Or just
use ipt_recent if you can come up with a rule to identify the attacker
w/o using iplimit.  To use ipt_recent you do:

# Bad guy in the list with activity less than 60 seconds ago..
iptables -A FORWARD -m recent --rcheck --seconds 60 --name badguy -j DROP 

# Check for bad guy, go to BADCHAIN if found..
iptables -A FORWARD -m limit --etcetc -j BADCHAIN 

# Bad guy detected!  Add his IP to the badguy list!
iptables -A BADCHAIN -m recent --set --name badguy -j DROP # Add IP to list

The ipt_recent module homepage is
http://snowman.net/projects/ipt_recent/

A pretty recent version (0.3.0) is also in netfilter CVS.  ipt_recent
0.3.1 is out and I expect it will be in netfilter CVS soon.  The primary
fix in 0.3.1 is TTL handling.

	Stephen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-01 20:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 17:34 deny cgi scanner Eric Marchionni
2003-04-01 17:47 ` Cedric Blancher
2003-04-01 19:43   ` Eric Marchionni
2003-04-01 20:06     ` Stephen Frost [this message]
2003-04-01 23:23       ` Arnt Karlsen
2003-04-02 12:54         ` Stephen Frost
2003-04-02 19:32           ` Arnt Karlsen
2003-04-01 18:17 ` Jesper Lund

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=20030401200652.GY18434@ns.snowman.net \
    --to=sfrost@snowman.net \
    --cc=blancher@cartel-securite.fr \
    --cc=mailing-lists@gmx.ch \
    --cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.