netdev - Re: [PATCH] IPv6 multicast routing

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: <20090127.223902.45013943.davem@davemloft.net>
Date:	Tue, 27 Jan 2009 22:39:02 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	thomas.goff@...ing.com
Cc:	netdev@...r.kernel.org, fred.l.templin@...ing.com
Subject: Re: [PATCH] IPv6 multicast routing

From: Tom Goff <thomas.goff@...ing.com>
Date: Tue, 20 Jan 2009 12:02:48 -0800

>   - Enable/disable IPv6 multicast forwarding on the corresponding
>     interface when a routing daemon adds/removes a multicast virtual
>     interface.

Since Hideaki-san is being unresponsive I looked at this patch again
so I can apply it, or at least part of it, to get the bugs fixed.

I disagree with his objection to the mc_forwarding changes here, they
are correct and in fact desirable.  They are desirable since without
this we have yet another disconnect between ipv4 and ipv6 behavior.

We already have way too many of those.

Every time I notice a behavior difference between our ipv4 and ipv6
stack I almost believe there is an active conspiracy to make the
transition to ipv6 as difficult as possible :-)

So I'm going to apply this patch as-is, with the addition of making
the mc_forwarding sysctl read-only (perms 0444) as it is in ipv4.
--
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