linux-kernel - Re: [PATCH] make ipv4 multicast packets only get delivered to sockets that are joined to group

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:	Wed, 13 Sep 2006 12:12:23 -0400
From:	Jeff Layton <jlayton@...chiereds.net>
To:	David Stevens <dlstevens@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] make ipv4 multicast packets only get delivered to
	sockets	that are joined to group

On Wed, 2006-09-13 at 07:32 -0700, David Stevens wrote:
> netdev-owner@...r.kernel.org wrote on 09/13/2006 07:13:55 AM:
>
>         This is not true on any OS I'm aware of, including the
> original sockets multicast implementation on early BSD.
> 

The current Linux behavior does seem to be consistent with the way
recent BSD and OSX seem to work. Solaris 8 seems to behave consistent
with the patch I posted.

Most of the RFC's I've looked at don't seem to have much to say about
how multicasting works at the socket level. Is there an RFC or
specification that spells this out, or is this one of those situations
where things are somewhat open to interpretation?

Thanks,
Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/