[PATCH] dbus-spec: introduce new PERMIT_INTERACTIVE_AUTHENTICATION
Thiago Macieira
thiago at kde.org
Thu Sep 4 09:20:57 PDT 2014
On Thursday 04 September 2014 13:28:19 David Herrmann wrote:
> If interactivity is part of a operation that is done by a method call,
> it is totally acceptable to add a method-argument that selects
> interactivity. This is unlike authorization, which it is part of the
> transmission layer (is the source allowed to perform that operation?),
> not part of the actual operation. Authorization needs to be done for
> *all* method calls (standard dbus policies). This flag extends this by
> optional interactive authentication. I don't see how this has anything
> to do with an interactivity-flag for the actually performed operation.
[...]
> If we make this flag generic, there is no way to disable
> interactive-auth but enable an interactive operation. Maybe you want a
> "save download" dialog, but without any interactive authentication.
Hi David
That's a good argument, thank you for saying it.
I still think we ought to give this a little more thought, but I won't object
anymore to the change in the spec.
Anyway, we have time until the next D-Bus library release containing the new
methods to set and unset the flag.
--
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
More information about the dbus
mailing list