public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@redhat.com>
Subject: Re: TCP-RST Vulnerability - Doubt
Date: Sat, 26 Jun 2004 04:22:44 +0200	[thread overview]
Message-ID: <40DCDDF4.7030509@tomt.net> (raw)
In-Reply-To: <20040625150532.1a6d6e60.davem@redhat.com>

David S. Miller wrote:
>>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.

Now you got me curious :-)

I have not seen anything conclusive on this yet. How sensitive is Linux 
to the attack? Some say it deals with it better than others did before 
they got "fixed", but with no hard evidence or a sensible explanation.

Lets assume you're on a FastEthernet pipe capable of delivering 144kpps. 
How "hard" would it be to exploit it in such a scenario, given we know 
the source port and approximate system time used on one of the ends?

Sure, on a FastEthernet your pipe is toast if someone really wants your 
arse anyway, but you don't want connections over other pipes, or 
internally, to die during such an attack.

-- 
Cheers,
André Tomt

  reply	other threads:[~2004-06-26  2:24 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 [this message]
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=40DCDDF4.7030509@tomt.net \
    --to=andre@tomt.net \
    --cc=davem@redhat.com \
    --cc=linux-kernel@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