From: "David S. Miller" <davem@redhat.com>
To: saiprathap <saiprathap@cc.usu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP-RST Vulnerability - Doubt
Date: Fri, 25 Jun 2004 15:05:32 -0700 [thread overview]
Message-ID: <20040625150532.1a6d6e60.davem@redhat.com> (raw)
In-Reply-To: <40DC9B00@webster.usu.edu>
On Fri, 25 Jun 2004 15:20:50 -0600
saiprathap <saiprathap@cc.usu.edu> wrote:
> I am a graduate research student majoring in the field of
> Computer Networking.As part of my research I have sorted out what FreeBSD has
> done to overcome the TCP-RST vulnerability (by modifying the stack to accept
> the RST packets only with the current + 1 sequence number and ignoring the
> rest, even if their sequence numbers fall within the receiving window).
>
> Could you kindly share your views regarding what Linux has done to its stack
> to overcome this vulnerability as it will be of great help to my research.
We have done nothing, and there are no plans to implement any workaround
for this problem.
RFC2385 MD5 hashing support is going in soon, and for the application where
the vulnerability actually matters (BGP sessions between backbone routers)
MD5 clears that problem right up and they're all using MD5 protection already
anyways.
next prev parent reply other threads:[~2004-06-25 22:07 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 [this message]
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
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=20040625150532.1a6d6e60.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.