GitLab

This makes it easier to write mechanisms as they don't have to watch
for the client requesting service vanishing.

For some weird reason.

All the functionality of polkit-1(1), sans managing the local
authority, is now available in pkaction(1) and pkcheck(1). In the
future we might want to add something like pklamanage(1) to manage the
local authority.

This is just a simple wrapper for the CheckAuthorization() D-Bus method.

See these messages

 https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01364.html
 https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01397.html

where this helper was discussed - it may make it a lot easier to use
polkit from code that pretends to care about OOM conditions.

Instead, just return the PolkitAuthorizationResult that already has
authorized==FALSE and challenge==TRUE.

This is because bindable GObject APIs should never return or accept a
GHashTable, see http://bugzilla.gnome.org/show_bug.cgi?id=581686#c6
for details.

Also remove the ObtainAuthorization() call and allow apps to pass
details to CheckAuthorization.

We might also want to expose methods on the D-Bus interface
org.freedesktop.PolicyKit1.AuthorityManager to configure this;
implementation-wise we'd just be writing out config files with a fixed
priority.

For now this is restricted to uid 0; going to revisit this when
hacking on the GNOME authorization UI.

Also add an example for this.

The thinking is that if someone wants to turn off PolicyKit, they
simply drop a file /etc/polkit-1/nullbackend.conf.d/99-i-hate-polkit.conf
with the contents

[Configuration]
priority=1000

This also provides a good cut-n-paste template / example etc. of how
to implement a PolicyKit backend.

Also add a short example to test this.

The session_id has got to be empty for now. The thinking is that in
the future we might want to register an authentication agent that runs
in secure desktop, e.g. a separate session from the user session.

make -j4 should work now