From: Florian Weimer <fw@deneb.enyo.de>
To: Lincoln Dale <ltd@cisco.com>
Cc: "David S. Miller" <davem@redhat.com>,
saiprathap <saiprathap@cc.usu.edu>,
linux-kernel@vger.kernel.org
Subject: Re: TCP-RST Vulnerability - Doubt
Date: Tue, 29 Jun 2004 23:27:00 +0200 [thread overview]
Message-ID: <874qou12e3.fsf@deneb.enyo.de> (raw)
In-Reply-To: <5.1.0.14.2.20040629122704.04958ec8@171.71.163.14> (Lincoln Dale's message of "Tue, 29 Jun 2004 12:34:01 +1000")
* Lincoln Dale:
> the vulnerabilities are real for any application/protocol which makes
> use of long-duration TCP sessions.
... *and* which hasn't got fast recovery from connection loss.
For example, NNTP uses long-lived TCP connections, but it is NOT
vulnerable because restart is very cheap.
Given the other benefits of fast recovery, it's better to concentrate
on that than to tack something on the TCP stack which only solves a
tiny subset of the problems (which isn't even relevant in practice).
prev parent reply other threads:[~2004-06-29 21:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 21:20 TCP-RST Vulnerability - Doubt saiprathap
2004-06-25 22:05 ` David S. Miller
2004-06-26 2:22 ` Andre Tomt
2004-06-28 19:18 ` Florian Weimer
2004-06-28 13:22 ` Miquel van Smoorenburg
2004-06-28 14:49 ` Chris Wedgwood
2004-06-28 18:34 ` Florian Weimer
2004-06-28 18:37 ` Willy Tarreau
2004-06-28 19:26 ` Florian Weimer
2004-06-29 20:03 ` Valdis.Kletnieks
2004-06-29 21:22 ` Florian Weimer
2004-06-29 21:45 ` Valdis.Kletnieks
2004-06-29 2:34 ` Daniel Roesen
2004-06-29 21:28 ` Florian Weimer
2004-06-29 2:34 ` Lincoln Dale
2004-06-29 21:27 ` Florian Weimer [this message]
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=874qou12e3.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltd@cisco.com \
--cc=saiprathap@cc.usu.edu \
/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