netdev - Re: [PATCH net 0/2] lwtunnel: make it really work, for IPv4

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: <20150923162927.6d437a1f@griffin>
Date:	Wed, 23 Sep 2015 16:29:27 +0200
From:	Jiri Benc <jbenc@...hat.com>
To:	ebiederm@...ssion.com (Eric W. Biederman)
Cc:	Thomas Graf <tgraf@...g.ch>, netdev@...r.kernel.org,
	Roopa Prabhu <roopa@...ulusnetworks.com>
Subject: Re: [PATCH net 0/2] lwtunnel: make it really work, for IPv4

On Wed, 23 Sep 2015 07:17:53 -0500, Eric W. Biederman wrote:
> Assuming the transport is UDP then it would be a UDP socket.  That
> socket will have all of the information needed to construct the outer
> header as the receive path of that socket removes the outer header.
> 
> I admit you can't use the cached dst.  It is the wrong on that socket.
> 
> My point is that if we have the UDP socket and we have the sk we have
> all of the information we need to compute the reverse dst.

That (single) UDP socket may represent many tunnels with different
parameters. Knowing the socket is still not enough to construct the
data. The only place where the needed data is stored is routing table
which won't help us much for ARP, and the metadata dst attached to the
incoming skb.

 Jiri

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