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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090416.151949.134404096.davem@davemloft.net>
Date:	Thu, 16 Apr 2009 15:19:49 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	cl@...ux.com
Cc:	dlstevens@...ibm.com, 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

From: Christoph Lameter <cl@...ux.com>
Date: Thu, 16 Apr 2009 17:04:30 -0400 (EDT)

> Can you give us a list of products that verifiably rely on the current
> behavior?

Christoph just drop this, we're not creating a system-wide default
selection that backs away from 15+ years of precedence.

Maybe Solaris has so few users that it's OK for them to go down
that path, but for us it's unacceptable to do things like this.

Fix your application.  And as David noted, it will be not only
more robust, but also still work on those "other systems."

So even your "works on all systems" argument is groundless.  If
you make it work under Linux it will in fact work on all systems,
and be more robust in the case of other applications using the
same multicast address and port.
--
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