Netdev List
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: netdev@oss.sgi.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tcp vulnerability?  haven't seen anything on it here...
Date: Wed, 21 Apr 2004 12:02:22 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0404211153550.1169@chaos> (raw)
In-Reply-To: <40869267.30408@nortelnetworks.com>

On Wed, 21 Apr 2004, Chris Friesen wrote:

>
> There has been some discussion about this on the Debian and OpenBSD
> lists, but I haven't seen anything on it here.  I know my boss is going
> to hear about this and want more information, so where does Linux stand
> with regards to this?
>
> http://www.uniras.gov.uk/vuls/2004/236929/index.htm
>
> Thanks,
>
> Chris

The vulnerabilities were discussed on US news reports as being
like somebody discovered they could disconnect your electricity
if they had some wire-cutters.

Those guys in the UK just don't have anything else to do! It
seems that they discovered that if you tap-into some network
physical media you could disrupt it! Since it has been taking
so long for IP/V6 to take hold, those proponents claim that
it will be a solution. Me-thinks it's a solution waiting for
a problem. The IP/V6 folks want to force (using government and
industry FUD) to discontinue IP/V4 as a "security risk!!!"

Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5557.45 BogoMips).
            Note 96.31% of all statistics are fiction.

  reply	other threads:[~2004-04-21 16:02 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 [this message]
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
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=Pine.LNX.4.53.0404211153550.1169@chaos \
    --to=root@chaos.analogic.com \
    --cc=cfriesen@nortelnetworks.com \
    --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