netdev - Re: PATCH: Multicast: Filter multicast traffic per socket mc

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:	Fri, 17 Apr 2009 09:56:04 -0400 (EDT)
From:	Christoph Lameter <cl@...ux.com>
To:	David Miller <davem@...emloft.net>
cc:	nhorman@...driver.com, netdev@...r.kernel.org,
	vladislav.yasevich@...com, dlstevens@...ibm.com
Subject: Re: PATCH: Multicast: Filter multicast traffic per socket mc_list

On Thu, 16 Apr 2009, David Miller wrote:

> No Christoph, do this right.
>
	> Linux by default will behave the way it has for 15+ years.  And if an
> application wants new behavior, you have to ask for it.
>
> End of story.

This is not right. All other OSes filter multicast traffic according to
the multicast groups subscribed too (and that includes the evil one).
There is no requirement of asking for "new" behavior. Why should multicast
applications have to add special code to request something that comes by
default on other platforms?

The old behavior does not seem to be usable anyways and its certainly
looks buggy if multicast packets are duplicated by the kernel and sent to
applications that never have asked for it. And OS should do the sane thing
by default and not only if someone asks for it.

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