From: Damjan <gdamjan@mail.net.mk>
To: netfilter@lists.netfilter.org
Cc: Jean-Marie <jm.nfilter@laposte.net>
Subject: Re: mangle + TCP Flags
Date: Thu, 11 Dec 2003 15:54:08 +0100 [thread overview]
Message-ID: <20031211145408.GB32747@legolas.on.net.mk> (raw)
In-Reply-To: <20031211105506.6c530c5a.jm.nfilter@laposte.net>
> >If a module like this existed it would be a great way to violate the
> >protocol and cause antisocial behaviour of your tcp stack.
>
> Yes, I agree, but in any case there would be more efficient ways to
> cause antisocial behaviour. In fact, in the beginning, my idea was to return a RST,ACK, for each SYN received on one of my closed ports, in order to make a scan tool belive that they are all open. (Perhaps it is useles but I found the idea amusing.
Maybe TARPIT is what you need?
Adds a TARPIT target to iptables, which captures and holds incoming TCP
connections using no local per-connection resources. Connections are
accepted, but immediately switched to the persist state (0 byte window),
in which the remote side stops sending data and asks to continue every
60-240 seconds. Attempts to close the connection are ignored, forcing the
remote side to time out the connection in 12-24 minutes.
--
Damjan Georgievski
jabberID: damjan@bagra.net.mk
next prev parent reply other threads:[~2003-12-11 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 9:55 mangle + TCP Flags Jean-Marie
2003-12-11 10:48 ` Maciej Soltysiak
2003-12-11 14:54 ` Damjan [this message]
2003-12-11 15:27 ` Jean-Marie Orset
2003-12-11 15:32 ` Jean-Marie Orset
2003-12-11 15:43 ` Antony Stone
2003-12-11 15:57 ` Jean-Marie Orset
-- strict thread matches above, loose matches on Subject: below --
2003-12-11 15:57 bmcdowell
2003-12-11 20:43 ` Maciej Soltysiak
2003-12-10 14:19 Jean-Marie
2003-12-10 16:31 ` Maciej Soltysiak
2003-12-10 19:25 ` Maciej Soltysiak
2003-12-10 19:38 ` Antony Stone
2003-12-10 10:08 Jean-Marie
2003-12-11 17:06 ` Tom Marshall
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=20031211145408.GB32747@legolas.on.net.mk \
--to=gdamjan@mail.net.mk \
--cc=jm.nfilter@laposte.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox