Re: [PATCH] Introduce the authorizer protocol

On Wed, 2 Dec 2015 12:28:33 +0200 Giulio Camuffo wrote: > 2015-11-26 10:21 GMT+02:00 Pekka Paalanen : > > On Wed, 25 Nov 2015 17:39:25 +0100 > > Mariusz Ceier wrote: > > > >> Hi, > >> > >> On 25 November 2015 at 16:14, Pekka Paalanen wrote: > >> > >> > On Tue, 24 Nov 2015 18:07:34 +0100 > >

Re: [PATCH] Introduce the authorizer protocol

2015-11-26 10:21 GMT+02:00 Pekka Paalanen : > On Wed, 25 Nov 2015 17:39:25 +0100 > Mariusz Ceier wrote: > >> Hi, >> >> On 25 November 2015 at 16:14, Pekka Paalanen wrote: >> >> > On Tue, 24 Nov 2015 18:07:34 +0100 >> > Mariusz Ceier wrote: >> > >> > > Hi, >> > > >> > > On 24 November 2015 at 17:

Re: [PATCH] Introduce the authorizer protocol

On Wed, 25 Nov 2015 17:39:25 +0100 Mariusz Ceier wrote: > Hi, > > On 25 November 2015 at 16:14, Pekka Paalanen wrote: > > > On Tue, 24 Nov 2015 18:07:34 +0100 > > Mariusz Ceier wrote: > > > > > Hi, > > > > > > On 24 November 2015 at 17:35, Giulio Camuffo > > > wrote: > > > > > > > 2015-1

Re: [PATCH] Introduce the authorizer protocol

Hi, On 25 November 2015 at 16:14, Pekka Paalanen wrote: > On Tue, 24 Nov 2015 18:07:34 +0100 > Mariusz Ceier wrote: > > > Hi, > > > > On 24 November 2015 at 17:35, Giulio Camuffo > > wrote: > > > > > 2015-11-24 18:16 GMT+02:00 Mariusz Ceier : > > > > Hi, > > > > How the clients will know: >

Re: [PATCH] Introduce the authorizer protocol

On Tue, 24 Nov 2015 18:07:34 +0100 Mariusz Ceier wrote: > Hi, > > On 24 November 2015 at 17:35, Giulio Camuffo > wrote: > > > 2015-11-24 18:16 GMT+02:00 Mariusz Ceier : > > > Hi, > > > How the clients will know: > > > a) which interface is restricted and which is not ? > > > > It doesn't

Re: [PATCH] Introduce the authorizer protocol

2015-11-24 20:53 GMT+02:00 Derek Foreman : > On 24/11/15 09:16 AM, Giulio Camuffo wrote: >> This new extension is used by clients wanting to execute priviledged >> actions such as taking a screenshot. >> The usual way of granting special priviledged to apps is to fork and >> exec them in the compos

Re: [PATCH] Introduce the authorizer protocol

On 24/11/15 09:16 AM, Giulio Camuffo wrote: > This new extension is used by clients wanting to execute priviledged > actions such as taking a screenshot. > The usual way of granting special priviledged to apps is to fork and > exec them in the compositor, and then checking if the client is the > kn

Re: [PATCH] Introduce the authorizer protocol

Hi, On 24 November 2015 at 17:35, Giulio Camuffo wrote: > 2015-11-24 18:16 GMT+02:00 Mariusz Ceier : > > Hi, > > How the clients will know: > > a) which interface is restricted and which is not ? > > It doesn't, but does it need to know it? It can still ask for > authorization even if the inte

Re: [PATCH] Introduce the authorizer protocol

2015-11-24 18:16 GMT+02:00 Mariusz Ceier : > Hi, > How the clients will know: > a) which interface is restricted and which is not ? It doesn't, but does it need to know it? It can still ask for authorization even if the interface is not. > b) that the compositor implements restricted interface

Re: [PATCH] Introduce the authorizer protocol

Hi, How the clients will know: a) which interface is restricted and which is not ? b) that the compositor implements restricted interface ? should they be visible in the registry ? If the client would like to use many restricted interfaces, it would have to issue multiple authorize requests - pr

[PATCH] Introduce the authorizer protocol

This new extension is used by clients wanting to execute priviledged actions such as taking a screenshot. The usual way of granting special priviledged to apps is to fork and exec them in the compositor, and then checking if the client is the known one when it binds the restricted global interface.