netdev - Re: [PATCH net-next v2] net: ipv6: make sure multicast packets are not forwarded beyond the different scopes

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]

Date:   Tue, 02 May 2017 14:59:23 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     donatas.abraitis@...il.com
Cc:     netdev@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH net-next v2] net: ipv6: make sure multicast packets are
 not forwarded beyond the different scopes

From: Donatas Abraitis <donatas.abraitis@...il.com>
Date: Thu, 27 Apr 2017 10:12:02 +0300

> 	    RFC4291 2.7 Routers must not forward any multicast packets
> 	    beyond of the scope indicated by the scop field in the
> 	    destination multicast address.
> 
> Signed-off-by: Donatas Abraitis <donatas.abraitis@...il.com>

I think it's a ">=" test which is needed here, not pure equality.
Scopes are subsets of other scopes and are therefore allowed within
eachother.

Did you actually see misbehavior due to this issue, or see a real
bonafide conformance test fail?

If you're just reading the RFC and sticking tests here and there based
upon what you read, without any testing or real life verification of
the issue, this is _strongly_ discouraged.

It would even be ok if you merely showed how another open source
networking stack makes this test.