public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: TCP-RST Vulnerability - Doubt
Date: Mon, 28 Jun 2004 13:22:37 +0000 (UTC)	[thread overview]
Message-ID: <cbp62t$a38$1@news.cistron.nl> (raw)
In-Reply-To: 20040625150532.1a6d6e60.davem@redhat.com

In article <20040625150532.1a6d6e60.davem@redhat.com>,
David S. Miller <davem@redhat.com> wrote:
>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.

MD5 protection on BGP sessions isn't very common yet. MD5 uses CPU,
and routers don't usually have much of that. Which means that now an
MD5 CPU attack is possible instead of a TCP RST attack.

The "TTL hack" solution is safer. Make sure sender uses a TTL
of 255, on the receiver discard all packets with a TTL < 255.
You can use iptables to implement that on a Linux box.

Mike.


  parent reply	other threads:[~2004-06-28 13:22 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 [this message]
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='cbp62t$a38$1@news.cistron.nl' \
    --to=miquels@cistron.nl \
    --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