From: Chris Friesen <cfriesen@nortelnetworks.com>
To: alex@pilosoft.com
Cc: jamal <hadi@cyberus.ca>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: tcp vulnerability? haven't seen anything on it here...
Date: Thu, 22 Apr 2004 11:42:51 -0400 [thread overview]
Message-ID: <4087E7FB.7000400@nortelnetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0404221030240.2738-100000@paix.pilosoft.com>
alex@pilosoft.com wrote:
> Nevertheless, number of packets to kill the session is still *large*
> (under "best-case" for attacker, you need to send 2^30 packets)...
I though the whole point of this vulnerability was that you "only" needed to send 64K packets, not 2^30.
Chris
next prev parent reply other threads:[~2004-04-22 15:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 15:25 tcp vulnerability? haven't seen anything on it here Chris Friesen
2004-04-21 16:02 ` Richard B. Johnson
2004-04-21 16:25 ` Chris Friesen
2004-04-21 17:03 ` Jörn Engel
2004-04-21 20:20 ` David S. Miller
2004-04-22 0:45 ` James Morris
2004-04-22 5:04 ` Willy Tarreau
2004-04-22 8:23 ` Giuliano Pochini
2004-04-22 11:35 ` Richard B. Johnson
2004-04-22 13:17 ` Willy Tarreau
2004-04-22 13:42 ` Richard B. Johnson
2004-04-22 14:18 ` Willy Tarreau
2004-04-22 20:25 ` Richard B. Johnson
2004-04-22 21:08 ` Willy Tarreau
2004-04-22 18:28 ` David S. Miller
2004-04-22 13:22 ` jamal
2004-04-22 13:46 ` Giuliano Pochini
2004-04-22 14:27 ` jamal
2004-04-22 14:37 ` alex
2004-04-22 15:17 ` jamal
2004-04-22 15:27 ` alex
2004-04-22 17:38 ` Horst von Brand
2004-04-22 21:15 ` Florian Weimer
2004-04-22 15:42 ` Chris Friesen [this message]
2004-04-22 15:47 ` alex
2004-04-23 10:31 ` Florian Weimer
2004-04-22 13:58 ` Florian Weimer
2004-04-23 13:55 ` Florian Weimer
2004-04-23 14:15 ` alex
2004-04-23 14:25 ` jamal
2004-04-22 20:01 ` Ranjeet Shetye
2004-04-22 21:26 ` Sridhar Samudrala
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=4087E7FB.7000400@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=alex@pilosoft.com \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).