netdev - Re: [PATCH] tcp: assign the sock correctly to an outgoing SYNACK packet

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: <1365443267.3887.28.camel@edumazet-glaptop>
Date:	Mon, 08 Apr 2013 10:47:47 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Paul Moore <pmoore@...hat.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	mvadkert@...hat.com
Subject: Re: [PATCH] tcp: assign the sock correctly to an outgoing SYNACK
 packet

On Mon, 2013-04-08 at 13:40 -0400, Paul Moore wrote:

> Sort of a similar problem, but not really the same.  Also, arguably, there is 
> no real associated sock/socket for a RST so orphaning the packet makes sense.  
> In the case of a SYNACK we can, and should, associate the packet with a 
> sock/socket.

What is the intent ?

This kind of requirement has a huge cost, and thats why I want a hook
instead of a 'generic thing'

Please read : 

http://workshop.netfilter.org/2013/wiki/images/3/3a/NFWS-TCP.pdf



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