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

2014-11-24 Thread Jussi Laako
On 19.11.2014 16:22, Pekka Paalanen wrote: When a session compositor is started, you can already use WAYLAND_SOCKET environment variable to pass an opened connection to it. If your system compositor forks session compositors, no problem. If something else starts your session compositors, you

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

2014-11-19 Thread Pekka Paalanen
(Fixing CC lists, please use reply-to-all in the future...) On Wed, 22 Oct 2014 10:55:25 +0300 Jussi Laako jussi.la...@linux.intel.com wrote: On 20.10.2014 18:13, Daniel Stone wrote: Each to their own; I don't think it's necessarily any more complex than split compositors, since at some

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

2014-10-22 Thread Jussi Laako
On 20.10.2014 18:13, Daniel Stone wrote: 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.

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

2014-10-20 Thread Jussi Laako
On 17.10.2014 20:00, Jason Ekstrand wrote: On Thu, Oct 16, 2014 at 9:23 AM, Imran Zaman imran.za...@gmail.com mailto:imran.za...@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

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

2014-10-20 Thread Daniel Stone
Hi, On 20 October 2014 15:19, Jussi Laako jussi.la...@linux.intel.com wrote: On 17.10.2014 20:00, Jason Ekstrand wrote: 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

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

2014-10-20 Thread Jussi Laako
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

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

2014-10-20 Thread Daniel Stone
Hi, On 20 October 2014 16:06, Jussi Laako jussi.la...@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

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

2014-10-17 Thread Jason Ekstrand
On Thu, Oct 16, 2014 at 9:23 AM, Imran Zaman imran.za...@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? Also, why are you doing this through environment variables and not

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

2014-10-16 Thread Imran Zaman
This is used for nested compositor architectures. Signed-off-by: Imran Zaman imran.za...@gmail.com --- src/wayland-server.c | 27 +++ 1 file changed, 27 insertions(+) diff --git a/src/wayland-server.c b/src/wayland-server.c index 09e8903..721fabe 100644 ---