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

On Thu, 16 Apr 2009, David Stevens wrote:

> This isn't what I suggested-- you have the default backwards. It must
> default
> to current behavior, or it's pointless.

If it would default to the current behavior then it would be incompatible
with the behavior of other operating systems and the surprising behavior
of the Linux multicast stack would continue to exist. The unusual behavior
needs to be switched on if wanted for legacy or other reasons.

> The text you have with it is overstated, too. Of course applications using
> your model can still receive unexpected data-- it does not reserve the
> port or multicast address to just your sender or to multicast traffic
> alone.

The application will no longer receive traffic from multicast groups that
it did not subscribe to. Yes unicast can still result in unexpected
traffic.
--
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