Netdev List
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: alex@pilosoft.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	Florian Weimer <fw@deneb.enyo.de>
Subject: Re: tcp vulnerability?  haven't seen anything on it here...
Date: 23 Apr 2004 10:25:32 -0400	[thread overview]
Message-ID: <1082730332.1027.57.camel@jzny.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0404231006440.8887-100000@paix.pilosoft.com>


Clarification:
I think the latency of my earlier email introduced by probably netdev is
creating a lot of "hostile" responses to me ;-> I feel like i am in
hostile path here ;->
I sent that email a long time ago, seems like netdev or my ISP decided
to deliver it now and reordered the delivery. This has happened to me a 
few times before with netdev thats why i prefer to cc people whenever i
can (worst case they receive more than one message)
Consider that message obsolete. I know you can create this problem via
brute force as you explained in your later email (that showed up
yesterday).

cheers,
jamal

On Fri, 2004-04-23 at 10:15, alex@pilosoft.com wrote:
> > And for something like a huge download to just regular joe, this is more
> > of a nuisance assuming some kiddie has access between you and the
> > server. OTOH, long lived BGP sessions are affected assuming you are
> > going across hostile path to your peer.
> Again - no hostile path necessary. Attack is brute-force and does not rely 
> on MITM.
> 
> > So whats all this ado about nothing? Local media made it appear we are
> > all about to die.
> Pretty much.
> > 
> > Is anyone working on some fix?
> In networking world, there was a craze of enabling TCP-MD5 for BGP
> sessions reacting to this attack. There is alternative solution, "TTL
> hack", relying that most BGP sessions are between directly-connected 
> routers, so if connection originator sets TTL to 255 and receiver verifies 
> that TTL on incoming packet is 255, you can be reasonably certain that the 
> packet was sent by someone directly connected to you. ;)
> 
> -alex
> 
> 

  reply	other threads:[~2004-04-23 14:25 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
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 [this message]
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=1082730332.1027.57.camel@jzny.localdomain \
    --to=hadi@cyberus.ca \
    --cc=alex@pilosoft.com \
    --cc=fw@deneb.enyo.de \
    --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