[PATCH 2/2] Support for adjusting socket access rights to allow group of users to connect to the socket.
jussi.laako at linux.intel.com
Mon Oct 20 07:19:09 PDT 2014
On 17.10.2014 20:00, Jason Ekstrand wrote:
> On Thu, Oct 16, 2014 at 9:23 AM, Imran Zaman <imran.zaman at gmail.com
> <mailto:imran.zaman at gmail.com>> wrote:
> This is used for nested compositor architectures.
> Could you please provide a little more explanation than that. What kind
> of nesting are you doing?
We have one system compositor using DRM backend and then nested
compositors for each user using wayland backend.
This is in order to share single GPU with multiple display outputs among
> Also, why are you doing this through environment variables and not
> something explicit? For instance, the compositor can easily grab the
> socket and chmod it. It has the privileges and knows what socket it is.
This is related to the other patch that allows modifying location of the
server/client socket location. I thought that the access control is best
being close to the place where socket is created. Otherwise it is hard
to follow what is going on if the related code is scattered across modules.
More information about the wayland-devel