netdev - Re: [PATCH v2 net-next 0/4] tunnels: fix incorrect IPv4/v6 headers interpretation

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: <20150829.130810.1498520909891590692.davem@davemloft.net>
Date:	Sat, 29 Aug 2015 13:08:10 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jbenc@...hat.com
Cc:	netdev@...r.kernel.org, tgraf@...g.ch, pshelar@...ira.com
Subject: Re: [PATCH v2 net-next 0/4] tunnels: fix incorrect IPv4/v6 headers
 interpretation

From: Jiri Benc <jbenc@...hat.com>
Date: Fri, 28 Aug 2015 20:48:18 +0200

> With tunneling, it is currently possible to get an IPv6 header and interpret
> it as an IPv4 header, or to interpret an IPv6 address as an IPv4 address
> (and vice versa). This leads to things like sending packets to incorrect
> address, IPv6 flow label being interpreted as IP packet length, etc.
> 
> Fix several places where this can happen.
> 
> Most of this is net-next only. The third patch affects net, too, but it
> doesn't seem there's anything in user space that sets the attribute at all
> currently, thus net-next is fine.
> 
> Changelog:
> v2: fixed geneve after incorrect rebase on top of Pravin's patches

Series applied, thanks Jiri.
--
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