From: Andi Kleen <andi@firstfloor.org>
To: Glenn Griffin <ggriffin.kernel@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add IPv6 support to TCP SYN cookies
Date: Tue, 5 Feb 2008 21:02:11 +0100 [thread overview]
Message-ID: <20080205200211.GA26150@one.firstfloor.org> (raw)
In-Reply-To: <c9e534200802051029u5d08cf6dm54866f769e362262@mail.gmail.com>
On Tue, Feb 05, 2008 at 10:29:28AM -0800, Glenn Griffin wrote:
> > Syncookies are discouraged these days. They disable too many
> > valuable TCP features (window scaling, SACK) and even without them
> > the kernel is usually strong enough to defend against syn floods
> > and systems have much more memory than they used to be.
> >
> > So I don't think it makes much sense to add more code to it, sorry.
>
> As you say the kernel is usually strong enough to defend against syn flood
> attacks, but what about the situations where it isn't? As valuable as the TCP
> features are I would give them up if it means I'm able to connect to my sshd
> port when I otherwise would be unable to. While increased synq sizes, better
> dropping algorithms, and minisocks are a great way to mitigate the attacks and
> in most cases are enough, there are situations where syncookies are nice.
Have you seen such a case in practice with a modern kernel?
They also cause problems unfortunately; e.g. there is no real flow control for connections
anymore in the non DOS case.
> Regardless, I would say as long as ipv4 has syncookie support it will
> accurately be viewed as a deficiency of ipv6 if it lacks support. So perhaps
> the discussion should be we whether all the other defenses are enough to
> warrant the removal of syncookie support from ipv4. That topic may bring in
> more opinions.
That is essentially what I and Alan were discussing.
>
> > Besides you should really move it to the ipv6 module, right now the code
> > would be always compiled in even for ipv4 only kernels.
>
> That is correct. I will gladly move it into it's own section within net/ipv6/.
> Do you have any problem using the same CONFIG and sysctl variables as the ipv4
> implementation?
No.
-Andi
next prev parent reply other threads:[~2008-02-05 19:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 23:01 [PATCH] Add IPv6 support to TCP SYN cookies Glenn Griffin
2008-02-05 15:55 ` Andi Kleen
2008-02-05 15:42 ` Alan Cox
2008-02-05 16:39 ` Andi Kleen
2008-02-05 16:03 ` Alan Cox
2008-02-05 16:48 ` Andi Kleen
2008-02-05 16:14 ` Alan Cox
2008-02-05 20:50 ` Willy Tarreau
2008-02-05 18:29 ` Glenn Griffin
2008-02-05 19:25 ` Ross Vandegrift
2008-02-05 20:11 ` Andi Kleen
2008-02-05 21:23 ` Ross Vandegrift
2008-02-06 8:53 ` Andi Kleen
2008-02-07 19:44 ` Ross Vandegrift
2008-02-08 12:07 ` Andi Kleen
2008-02-12 20:38 ` Ross Vandegrift
2008-02-05 20:02 ` Andi Kleen [this message]
2008-02-05 20:39 ` Evgeniy Polyakov
2008-02-05 20:53 ` Andi Kleen
2008-02-05 21:50 ` Evgeniy Polyakov
2008-02-05 21:20 ` Alan Cox
2008-02-05 21:52 ` Evgeniy Polyakov
2008-02-05 21:20 ` Willy Tarreau
2008-02-05 22:05 ` Alan Cox
2008-02-06 1:52 ` Glenn Griffin
2008-02-06 7:50 ` Andi Kleen
2008-02-06 17:36 ` Glenn Griffin
2008-02-06 18:45 ` Andi Kleen
2008-02-06 23:03 ` Glenn Griffin
2008-02-06 9:13 ` Evgeniy Polyakov
2008-02-06 18:30 ` Glenn Griffin
2008-02-07 7:24 ` Evgeniy Polyakov
2008-02-07 9:40 ` Eric Dumazet
2008-02-08 5:32 ` Glenn Griffin
2008-02-08 5:49 ` Glenn Griffin
2008-02-11 16:07 ` YOSHIFUJI Hideaki / 吉藤英明
2008-02-18 23:45 ` Glenn Griffin
2008-02-13 7:31 ` YOSHIFUJI Hideaki / 吉藤英明
2008-02-05 19:57 ` Jan Engelhardt
2008-02-05 21:25 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2008-02-04 23:01 Glenn Griffin
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=20080205200211.GA26150@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ggriffin.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).