Bug 69980 - Misleading RegisterAuthenticationAgent documentation
Summary: Misleading RegisterAuthenticationAgent documentation
Status: RESOLVED MOVED
Alias: None
Product: PolicyKit
Classification: Unclassified
Component: daemon (show other bugs)
Version: unspecified
Hardware: Other All
: medium minor
Assignee: David Zeuthen (not reading bugmail)
QA Contact: David Zeuthen (not reading bugmail)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-30 19:26 UTC by Miloslav Trmac
Modified: 2018-08-20 21:36 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miloslav Trmac 2013-09-30 19:26:59 UTC
In data/org.freedesktop.PolicyKit1.Authority.xml, RegisterAuthenticationAgent documentation includes

> <para>Note that current versions of PolicyKit will only work if @session_id is set to the empty string. In the future it might work for non-empty strings if the caller is sufficiently privileged.</para>

This is from an earlier version of the API, session_id was removed in

> commit 36fc7a6d358c1d373c181191da6265a538a71dae
> Author: David Zeuthen <davidz@redhat.com>
> Date:   Mon Jul 20 18:49:25 2009 -0400
> 
>     Add support for querying and revoking temporary authorizations
>     
>     Also change how authentication agents are registered (take a Subject
>     instead of the session-id) and add convenience functions to
>     asynchronously construct a PolkitUnixSession object given a process id
>     (by querying ConsoleKit).

Probably should remove the Note paragraph as well.
Comment 1 GitLab Migration User 2018-08-20 21:36:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/polkit/polkit/issues/32.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.