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

Jussi Laako jussi.laako at linux.intel.com
Mon Oct 20 08:06:47 PDT 2014

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.

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.

> Doing it through environment variables is just plain nasty though; I
> really don't like this patch. I'd much rather see an explicit call, or
> users creating the appropriate fd and then just passing it to the lib.

OK, then I think it would be better to move the socket creation out from 
libwayland and just pass the socket descriptor to libwayland.

More information about the wayland-devel mailing list