linux-kernel - Re: [PATCH 1/3] lib/kobject_uevent.c: disable broadcast of uevents to other namespaces

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: <55F31B99.2020907@alcatel-lucent.com>
Date:	Fri, 11 Sep 2015 14:21:13 -0400
From:	Michael J Coss <michael.coss@...atel-lucent.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	gregkh@...uxfoundation.org, davem@...emloft.net,
	linux-kernel@...r.kernel.org, containers@...ts.linuxcontainers.org,
	serge.hallyn@...ntu.com, stgraber@...ntu.com
Subject: Re: [PATCH 1/3] lib/kobject_uevent.c: disable broadcast of uevents to
 other namespaces

On 9/10/2015 8:36 PM, Eric W. Biederman wrote:
> "Michael J. Coss" <michael.coss@...atel-lucent.com> writes:
>
>> Restrict sending uevents to only those listeners operating in the same
>> network namespace as the system init process.  This is the first step
>> toward allowing policy control of the forwarding of events to other
>> namespaces in userspace.
> This limitation whould be better if we only skipped network namespaces
> where you are sending spoofed uevents.
>
> As it sits this has the possibility to break userspace.
>
> Eric
>
While I don't necessarily see how this could cause an issue with
userspace, I agree that it could be made to work that way and accomplish
the same goal and be even more transparent.  I would think that it would
require some state in the network namespace that would be settable to
say enable/disable host uevent broadcasts across this particular netlink
socket.

---Michael J Coss
--
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/