linux-kernel - Re: [PATCH] drivers: connector: cn_proc: allow limiting certain messages

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]

Message-Id: <20200218.123546.666027846950664712.davem@davemloft.net>
Date:   Tue, 18 Feb 2020 12:35:46 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     danielwa@...co.com
Cc:     zbr@...emap.net, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers: connector: cn_proc: allow limiting certain
 messages

From: "Daniel Walker (danielwa)" <danielwa@...co.com>
Date: Tue, 18 Feb 2020 16:30:36 +0000

> It's multicast and essentially broadcast messages .. So everyone gets every
> message, and once it's on it's likely it won't be turned off. Given that, It seems
> appropriate that the system administrator has control of what messages if any
> are sent, and it should effect all listening for messages.
> 
> I think I would agree with you if this was unicast, and each listener could tailor
> what messages they want to get. However, this interface isn't that, and it would
> be considerable work to convert to that.

You filter at recvmsg() on the specific socket, multicast or not, I
don't understand what the issue is.