Bug 22360

Summary: PolicyKit.conf should support <match group="groupname">
Product: PolicyKit Reporter: Josh Triplett <josh>
Component: libpolkitAssignee: David Zeuthen (not reading bugmail) <zeuthen>
Status: RESOLVED FIXED QA Contact: David Zeuthen (not reading bugmail) <zeuthen>
Severity: enhancement    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Josh Triplett 2009-06-19 00:13:02 UTC
PolicyKit.conf currently only supports matching on usernames and on action identifiers.  I'd also like to configure PolicyKit based on group names.  I propose doing so via a new "group" attribute on the match element, which would look like <match group="groupname">.

This would allow PolicyKit's configuration to take advantage of the information in /etc/group rather than duplicating it.
Comment 1 Josh Triplett 2009-06-19 00:14:26 UTC
(Originally reported in the Debian bug-tracking system: http://bugs.debian.org/533598 )
Comment 2 David Zeuthen (not reading bugmail) 2009-10-21 10:40:09 UTC
This bug report is for the old version of PolicyKit. Closing as all of the code has been rewritten. Please reopen if the bug report applies to the latest version of PolicyKit. Thanks.
Comment 3 Josh Triplett 2009-10-21 11:58:54 UTC
I never figured I'd need to point at http://www.jwz.org/doc/cadt.html, but apparently I do.  Not complaining about the rewrite, but old bug reports don't magically become irrelevant or invalid because you've written new code.  If you wanted confirmation that the bug still existed in the current version, you could have gone with "MOREINFO" and not "RESOLVED INVALID".

In any case, having actually checked whether the bug applies, it would appear from the documentation that the authorization system in the new policykit-1 supports matching both group and user identities.  Changing resolution to "FIXED".  Thank you for the fix.

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.