netdev - Re: [RFC][PATCH 1/1] cxgb3i: cxgb3 iSCSI initiator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <489DA3F9.1080703@opengridcomputing.com>
Date:	Sat, 09 Aug 2008 09:04:41 -0500
From:	Steve Wise <swise@...ngridcomputing.com>
To:	David Miller <davem@...emloft.net>
CC:	jgarzik@...ox.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

David Miller wrote:
> 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.
>   

I think a lot of these _could_ be implemented and integrated with the 
standard tools.





--
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