From: Patrick McHardy <kaber@trash.net>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: iptables STILL incorrectly using TCP packet contents without checking header!
Date: Sun, 03 Apr 2005 20:34:14 +0200 [thread overview]
Message-ID: <42503726.2030202@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0504010125500.24131@filer.marasystems.com>
Henrik Nordstrom wrote:
> On Thu, 31 Mar 2005, Jonas Berlin wrote:
>
>> But what will be done in case REJECT notices it's not valid?
>
>
> In such case REJECT should silently DROP the packet without sending a
> reject response.
>
> Same as you see in a TCP/IP stack when receiving malformed TCP packets.
> These are dropped as invalid, not generating TCP RST like most "odd but
> not malformed" TCP packets do.
Agreed. I'll fix it up.
Regards
Patrick
next prev parent reply other threads:[~2005-04-03 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 18:57 iptables STILL incorrectly using TCP packet contents without checking header! Simon Kirby
2005-03-31 20:04 ` Jonas Berlin
2005-03-31 23:27 ` Henrik Nordstrom
2005-04-03 18:34 ` Patrick McHardy [this message]
2005-04-01 0:03 ` Simon Kirby
2005-04-05 14:24 ` Amin Azez
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=42503726.2030202@trash.net \
--to=kaber@trash.net \
--cc=hno@marasystems.com \
--cc=netfilter-devel@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.