From: Ben Greear <greearb@candelatech.com>
To: Andi Kleen <ak@suse.de>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] [1/1] Deprecate tcp_tw_{reuse,recycle}
Date: Wed, 30 Jan 2008 11:22:29 -0800 [thread overview]
Message-ID: <47A0CE75.5080200@candelatech.com> (raw)
In-Reply-To: <20080130938.523292915@suse.de>
Andi Kleen wrote:
> We've recently had a long discussion about the CVE-2005-0356 time stamp denial-of-service
> attack. It turned out that Linux is only vunerable to this problem when tcp_tw_recycle
> is enabled (which it is not by default).
>
> In general these two options are not really usable in today's internet because they
> make the (often false) assumption that a single IP address has a single TCP time stamp /
> PAWS clock. This assumption breaks both NAT/masquerading and also opens Linux to denial
> of service attacks (see the CVE description)
>
> Due to these numerous problems I propose to remove this code for 2.6.26
We use these features to enable creating very high numbers of short-lived
TCP connections, primarily used as a test tool for other network
devices.
Perhaps just document the adverse affects and/or have it print out a warning
on the console whenever the feature is enabled?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2008-01-30 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 8:38 [PATCH] [1/1] Deprecate tcp_tw_{reuse,recycle} Andi Kleen
2008-01-30 19:22 ` Ben Greear [this message]
2008-01-31 2:59 ` Andi Kleen
2008-01-31 6:37 ` Ben Greear
2008-01-31 6:55 ` Andi Kleen
2008-01-31 16:41 ` Ben Greear
2008-01-31 16:49 ` Andi Kleen
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=47A0CE75.5080200@candelatech.com \
--to=greearb@candelatech.com \
--cc=ak@suse.de \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).