[19527] in bugtraq
Re: Loopback and multi-homed routing flaw in TCP/IP stack.
daemon@ATHENA.MIT.EDU (Crist Clark)
Tue Mar 6 21:56:58 2001
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <3AA580A5.D78FF744@globalstar.com>
Date: Tue, 6 Mar 2001 16:28:21 -0800
Reply-To: Crist Clark <crist.clark@GLOBALSTAR.COM>
From: Crist Clark <crist.clark@GLOBALSTAR.COM>
X-To: bert hubert <ahu@DS9A.NL>
To: BUGTRAQ@SECURITYFOCUS.COM
bert hubert wrote:
[snip]
> I still feel that this is a pretty stupid oversight - if routing is switched
> off as it SHOULD or even MUST be on a host, this is not supposed to happen.
People keep saying this and I don't think they mean it. "ROUTING" is
never turned off on host doing IP (at least I can't think of a counter-
example). Your average host probably has a default route, it has a loopback
route, lots of hosts have a m-cast route, etc. Multihomed hosts are always
going to have even more complicated routing tables.
I think you mean, "if FORWARDING is switched off..."
--
Crist J. Clark Network Security Engineer
crist.clark@globalstar.com Globalstar, L.P.
