[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANq1E4QafuvVU3i2GSah20Am1xvRTvuWRNo73ukwV-2MELj02g@mail.gmail.com>
Date: Wed, 22 Apr 2015 15:46:57 +0200
From: David Herrmann <dh.herrmann@...il.com>
To: Andy Lutomirski <luto@...capital.net>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Tom Gundersen <teg@...m.no>, Jiri Kosina <jkosina@...e.cz>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Daniel Mack <daniel@...que.org>,
Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: Issues with capability bits and meta-data in kdbus
Hi
On Wed, Apr 22, 2015 at 5:19 AM, Andy Lutomirski <luto@...capital.net> wrote:
> Where do you draw the line?
User-space draws _this_ line.
A bus creator can set the "mandatory metadata mask" of a bus. It
defines a mask all senders (!) have to use as base. The bus creator
can thus mandate a policy for its bus and force everyone who wants to
communicate via this bus to at least agree to transmit the requested
set of information. Using UIDs+GIDs+PIDs+seclabel+names as masks works
just fine.
To be clear, kdbus only transmits metadata that sender and receiver
both agreed on. Both peers have to opt-in for an item to be
transmitted.
Thanks
David
--
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/
Powered by blists - more mailing lists