[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080809.002840.167363463.davem@davemloft.net>
Date: Sat, 09 Aug 2008 00:28:40 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jgarzik@...ox.com
Cc: swise@...ngridcomputing.com, divy@...lsio.com, rdreier@...co.com,
kxie@...lsio.com, netdev@...r.kernel.org,
open-iscsi@...glegroups.com, michaelc@...wisc.edu,
daisyc@...ibm.com, wenxiong@...ibm.com, bhua@...ibm.com,
dm@...lsio.com, leedom@...lsio.com, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 1/1] cxgb3i: cxgb3 iSCSI initiator
From: Jeff Garzik <jgarzik@...ox.com>
Date: Fri, 08 Aug 2008 18:15:41 -0400
> * security updates for TCP problems mean that a single IP address can be
> PARTIALLY SECURE, because security updates for kernel TCP stack and
> h/w's firmware are inevitably updated separately (even if distributed
> and compiled together). Yay, we are introducing a wonderful new
> security problem here.
>
> * from a security, network scanner and packet classifier point of view,
> a single IP address no longer behaves like Linux. It behaves like
> Linux... sometime. Depending on whether it is a magic TCP port or not.
I agree with everything Jeff has stated.
Also, I find it ironic that the port abduction is being asked for in
order to be "compatible with existing tools" yet in fact this stuff
breaks everything. You can't netfilter this traffic, you can't apply
qdiscs to it, you can't execut TC actions on them, you can't do
segmentation offload on them, you can't look for the usual TCP MIB
statistics on the connection, etc. etc. etc.
It is broken from every possible angle.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists