[PATCH] dbus-spec: introduce new PERMIT_INTERACTIVE_AUTHENTICATION

[Thiago Macieira]

On Thursday 04 September 2014 02:01:43 Lennart Poettering wrote:
> Well, we have an immediate need now for the auth interactive flag, and
> auth is something that happens for a large number of methods as simple
> part of the operation. That's why dbus has policy already built in,
> and why polkit exists, to make it easy to do auth for methods offered
> via the bus.
> 
> This is different for something like your suggested "save-dialog"
> flag, because that is a very specific thing, showing save dialogs via
> bus methods calls is not a common property of all method calls, it's a
> very exceptional one.

Those are just two cases that came to mind looking at how KDE does things 
*today*. So it's not exceptional, it's real and current.

I save downloads more often than I need polkit authentication.

> Also see the example I gave in the other mail, that it matters why
> client need to be able to know that it is interactive *auth* that they
> disable, nothing else.

I must have missed that. How will the callee react to a call that needs 
authentication but didn't specify the flag (that is, 100% of the calls being 
placed today)?

> I mean, if such a entirely generic interactivity flag makes sense one
> day, we can add that too, but for now, let's focus on what we really
> need right now, where we have existing usecases.

I'm simply extending the use-case to other, very similar problems. It doesn't 
seem to me that this problem is of authentication, but of user lengthy 
interaction.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358