From: "David S. Miller" <davem@redhat.com>
To: michael@linuxmagic.com
Cc: kernel@pineview.net, linux-kernel@vger.kernel.org
Subject: Re: No more DoS
Date: Thu, 21 Dec 2000 20:53:13 -0800 [thread overview]
Message-ID: <200012220453.UAA12313@pizda.ninka.net> (raw)
In-Reply-To: <0012212020061G.24471@mistress> (message from Michael Peddemors on Thu, 21 Dec 2000 20:20:06 -0800)
In-Reply-To: <977453684.3a42c2744fbb7@ppro.pineview.net> <200012220200.SAA05057@pizda.ninka.net> <0012212020061G.24471@mistress>
From: Michael Peddemors <michael@linuxmagic.com>
Date: Thu, 21 Dec 2000 20:20:06 -0800
> I think not holding onto any state for an incoming SYN is nothing but
> a dream in any serious modern TCP implementation. It can be reduced,
> but not eliminated. The former is what most modern stacks have done
> to fight these problems.
A dream, maybe .... but hey so were most things that we now take for granted..
Worth kicking around a bit tho...
At a minimum you have to remember the MSS value given by the remote
host in the initial SYN, it is impossible to avoid this and provide
a TCP implementation of any level of quality.
The foundations of this person's scheme simply cannot work.
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-22 5:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 2:24 No more DoS Mike OConnor
2000-12-22 2:00 ` David S. Miller
2000-12-22 4:20 ` Michael Peddemors
2000-12-22 4:53 ` David S. Miller [this message]
2000-12-22 2:36 ` Tom Vier
2000-12-22 4:09 ` Michael Peddemors
2000-12-22 4:55 ` Michael H. Warfield
2000-12-22 18:21 ` kuznet
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=200012220453.UAA12313@pizda.ninka.net \
--to=davem@redhat.com \
--cc=kernel@pineview.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@linuxmagic.com \
/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).