[PATCH 2/2] Support for adjusting socket access rights to allow group of users to connect to the socket.

Daniel Stone daniel at fooishbar.org
Mon Oct 20 08:13:43 PDT 2014


On 20 October 2014 16:06, Jussi Laako <jussi.laako at linux.intel.com> wrote:

> On 20.10.2014 17:26, Daniel Stone wrote:
>> Makes sense, although you can already enforce isolation with a single
>> shared compositor ...
> Only weston can access the DRM compositor socket since it's the only one
> having group privileges for doing it. So each user has their own contained
> environment. DRM compositor is using fullscreen-shell and nested ones are
> using what ever other shell they wish.

weston-launch should be taking care of the privileges for you anyway ...

> We looked into input methods splitting with a shared compositor but it was
> getting a bit too complex. So now each nested compositor will manage their
> own set of input devices.
> So we have a functional setup with two displays, two mice, two keyboards
> and a touch screen. With the current approach. Two users have two mouse
> pointers and can type on the keyboard same time and window focus management
> and such works without modifications.

Each to their own; I don't think it's necessarily any more complex than
split compositors, since at some point you have to deal with input
splitting anyway, and if you want both security (i.e. random users not
opening random devices) and performance (i.e. no unnecessary hops through
input compositor for events), you end up having to deal with input
splitting in your system compositor anyway.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20141020/4eb44741/attachment.html>

More information about the wayland-devel mailing list