netdev - Re: [PATCH net-next] mpls: Enforce payload type of traffic sent using explicit NULL

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] [day] [month] [year] [list]

Message-Id: <20150809.225154.436246305394293337.davem@davemloft.net>
Date:	Sun, 09 Aug 2015 22:51:54 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rshearma@...cade.com
Cc:	netdev@...r.kernel.org, ebiederm@...ssion.com, tgraf@...g.ch,
	roopa@...ulusnetworks.com
Subject: Re: [PATCH net-next] mpls: Enforce payload type of traffic sent
 using explicit NULL

From: Robert Shearman <rshearma@...cade.com>
Date: Thu, 6 Aug 2015 11:04:56 +0100

> RFC 4182 s2 states that if an IPv4 Explicit NULL label is the only
> label on the stack, then after popping the resulting packet must be
> treated as a IPv4 packet and forwarded based on the IPv4 header. The
> same is true for IPv6 Explicit NULL with an IPv6 packet following.
> 
> Therefore, when installing the IPv4/IPv6 Explicit NULL label routes,
> add an attribute that specifies the expected payload type for use at
> forwarding time for determining the type of the encapsulated packet
> instead of inspecting the first nibble of the packet.
> 
> Signed-off-by: Robert Shearman <rshearma@...cade.com>

Applied, thanks.
--
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